© 2015 X2Engine Inc.
Difference between revisions of "Known Issues"
(→Troubleshooting) |
(→Troubleshooting) |
||
Line 20: | Line 20: | ||
All versions, on GoDaddy hosting | All versions, on GoDaddy hosting | ||
| | | | ||
− | All web applications | + | All web applications featuring human-friendly URLs (i.e. Joomla!, Drupal, Wordpress) will have this issue on GoDaddy. It is caused by the URL rewriting engine being disabled in GoDaddy's hosting environment. See the following articles on how to rectify the issue using <tt>.htaccess</tt> overrides: |
− | |||
* [http://www.magentocommerce.com/wiki/groups/227/error/no_input_file_specified Magento: "No Input File Specified"] | * [http://www.magentocommerce.com/wiki/groups/227/error/no_input_file_specified Magento: "No Input File Specified"] | ||
+ | * [http://support.godaddy.com/help/article/6656/enabling-joomla-search-engine-friendly-urls GoDaddy — Enabling Joomla! Search Engine Friendly URLs] | ||
|- | |- | ||
! scope="row" | Update notifications do not work | ! scope="row" | Update notifications do not work |
Revision as of 23:13, 18 December 2012
This page is a work in progress. As new common/recurring issues are encountered, they will be addressed here.
Troubleshooting
Description | Affected Instances | How to Fix |
---|---|---|
Installation error: deprecated function "mysql_escape_string" |
All versions up to 2.2.1 on some servers |
Replace all instances of "mysql_escape_string" with "addslashes" in initialize.php, or simply remove those function calls. Note that if you perform the latter action, you must ensure that the values you put in the "Application Name" and "Administrator Email" fields of the installation form do not contain any apostrophes (otherwise, the resulting installation will be broken). |
"No input file specified" |
All versions, on GoDaddy hosting |
All web applications featuring human-friendly URLs (i.e. Joomla!, Drupal, Wordpress) will have this issue on GoDaddy. It is caused by the URL rewriting engine being disabled in GoDaddy's hosting environment. See the following articles on how to rectify the issue using .htaccess overrides: |
Update notifications do not work |
|
|
Cannot view or create quotes |
|
Run the following SQL: Versions earlier than 2.0: INSERT INTO x2_fields (modelName, fieldName, attributeLabel, modified, custom, type, required, readOnly, linkType, searchable, relevance)
VALUES ("Quote", "products", "Products", 0, 0, "varchar", 0, 0, NULL, 0, ""),
("Quote", "existingProducts", "Existing Products", 0, 0, "varchar", 0, 0, NULL, 0, "")
Versions 2.0 and later: INSERT INTO x2_fields (modelName, fieldName, attributeLabel, modified, custom, type, required, readOnly, linkType, searchable, relevance,isVirtual)
VALUES ("Quote", "products", "Products", 0, 0, "varchar", 0, 0, NULL, 0, "", 1),
("Quote", "existingProducts", "Existing Products", 0, 0, "varchar", 0, 0, NULL, 0, "", 1)
|
Running Updates Manually
In some cases, it may be desirable to bypass the update notifications and go straight to the updater to check if there is a new version available, because of update notifications disabled or an improperly set unique_id in the x2_admin table. To run an update or check for an update manually, log in as the admin user and in the browser's address bar, replace "index.php/site/whatsNew" with "index.php/admin/updater", and hit enter to run the action.
In versions 2.2 and later, it is possible to go directly to the updater through a link in the admin console under the "System Settings" section.