{"id":738,"date":"2018-12-15T06:43:44","date_gmt":"2018-12-15T14:43:44","guid":{"rendered":"http:\/\/blogs.magicjudges.org\/judgeapps\/?p=738"},"modified":"2019-05-05T12:13:04","modified_gmt":"2019-05-05T19:13:04","slug":"judgeapps-updates-november-2018","status":"publish","type":"post","link":"https:\/\/blogs.magicjudges.org\/judgeapps\/2018\/12\/15\/judgeapps-updates-november-2018\/","title":{"rendered":"JudgeApps Updates – November 2018"},"content":{"rendered":"

Hello everyone and welcome to this month’s edition of what is new in JudgeApps land. This month we have a new review type and an update to our text editor. Caching was added to a few more sections of JudgeApps, as well as a bunch of performance upgrades to the site.<\/span><\/p>\n

Events <\/span><\/h1>\n

We start with a new upgrade to general posting in JudgeApps. For that we upgraded the TinyMCE, the text editor used throughout the site to post. This upgraded version will provide a better user experience when users are creating or editing events, as well as when editing project descriptions and the \u201cabout me\u201d section of their profile. We expanded the text editor window to give you more space to work with and less issues relating to text and images not showing at the right places when posting.<\/span><\/p>\n

Also on the note of events forums, there was seemly an error regarding access to said forums. While event participants like judges and staff had no issues, individuals who were supposed to be able to see said forums due to positions within the program, like RCs, didn\u2019t seem to be able to view the new \u201cmiscellaneous\u201d forum in some cases. This happened since the official forum properly gave those users access,but the miscellaneous event forum didn\u2019t. This is now sorted and shouldn\u2019t be a problem in the future.<\/span><\/p>\n

We also noticed that in some cases files uploaded to event pages are given the wrong file name. When \u201creplacing\u201d one file with another, the new file would be saved using the old file\u2019s name, including the extension. This code was changed to prevent this from occurring and now all files should appear with the name the file had when uploaded.<\/span><\/p>\n

User Accounts<\/span><\/h1>\n

Remember the TinyMCE from last section? That gave us the added advantage that now we can also have the \u201cabout me\u201d section of the user profile larger and more comfortable to use. This section should now be fitted to the size of the screen.<\/span><\/p>\n

Performance Upgrades<\/span><\/h1>\n

We added a few more caching functions to the site. This should help in a few areas, including site loading time. Since some portions of the site don\u2019t necessarily change whenever a user loads a new page, caching will use the existing data available to it instead of requesting all the data from JudgeApps again without reason.<\/span><\/p>\n

In some cases, this new cache caused the number of notifications shown to users to appear incorrectly. This was fixed. Another issue was that forum posts were cached without taking time zones into consideration, causing some posts to be shown out-of-order. This was fixed as well.<\/span><\/p>\n

For forum posts search we also refined the search process for them in order to reduce the search time that might be required to find a specific users recent forum posts and improved the way recent forum posts are presented.<\/span><\/p>\n

For specific user posts, up to this point the site would search all forum posts taking into account a lot of irrelevant posts, from closed forums for example, an action that would increase the search time for no reason. This has now improved and shouldn\u2019t take as long to resolve.<\/span><\/p>\n

As for recent forum posts, the relevant query was also updated and should be less resource consuming in the future. We also made upgrades to the judge search function making it less resource consuming and more efficient for searches that include multiple variables.<\/span><\/p>\n

Reviews<\/span><\/h1>\n

We added a new review type to the site \u2013 the GP Head Judge review for Team Leads. This mandatory review submitted by a GPHJ for each of their Team Leads has now received its own type of review, allowing us to ensure that the GPHJ Lead has the ability to see all of those reviews, and allowing us to track those reviews for the GPHJ Renewal process.<\/span><\/p>\n

A different issue in the field of reviews was that very rarely, while editing reviews, a hidden field would be submitted blank instead of containing the needed information, causing a \u00a0server error. We still don\u2019t know why this was happening, but we\u2019ve added a safety check to the code that handles review edits, and if this field is missing, we use our best guess of its information instead of just returning the error.<\/span><\/p>\n

Other Updates<\/span><\/h1>\n