Pending Critical Fixes
Below is a list of issues we are working on based on initial diagnostics from dozens of beta installations:
For those who have been struggling with mod_rewrite, you may be able to fix the issue yourself:
After struggling with this issue on a few hosts, we have discovered the cause. Some servers require a RewriteBase setting to be applied in the .htaccess file, which basically sets the base path of rewrite rules. If you are having problems with mod_rewrite ("white tree", assets not loading or pages not loading), then try to open the .htaccess file and comment out the rule: rewriteBase / (approximately line 29):
Unfortunately, we can't set this by default, because it will break servers that have correct defaults, and also because the path depends on the subfolder path where you may have uploaded X3. We will instead try to create improved detection in the diagnostics page, and recommend this feature if it seems necessary.
# If you are running from a subdirectory, your rewritebase should match the name of the path to where X3 is stored. # RewriteBase / # example1 - if running x3 in domain root, # RewriteBase /x3 # example2 - if running from a root folder named 'x3', RewriteBase /
There has been a couple of servers serving incorrect paths and links when using X3 in a subfolder. We are still not entirely sure why the code fails, but we have been able to find a better implementation. This will be fixed in 0.5.
Critical Panel bug
We have an issue reported for the admin from two users, where a copy- or move action starts creating unlimited recursive folders. This is critical because it will create an incredibly deep unwanted folder branch, which will is so deep that it can break both the frontend and backend from running. Although this issue is server-related, you may wish to avoid move+copy actions until it is fixed.
We have also uncovered the fact that most modern servers don't need chmod 777 permissions applied to folders that X3 needs to write to. Most servers that are configured correctly and have the same user-ID for _FTP and _WWW, don't need permissions set at all. In fact, setting chmod 777 on some servers will create a server error because of some security implementation. We need to add better documentation- and tests to check if permissions are required to be set, before you actually set them incorrectly ...
Next update should be out within Tuesday, and hopefully we can get these issues solved.