Search the Community
Showing results for tags 'patch'.
Found 8 results
-
There is an issue present in 4.2 the prevents users from importing records. This is due to some legacy code that was not removed. Note: this error will only arise if your php.ini error reporting settings include E_NOTICE. Users who are excluding notices should not encounter this issue, e.g.: error_reporting = E_ALL & ~E_NOTICE This is due to the undeclared variable left over in the code. To patch your instance, copy the attached processModels.php file into your X2Engine web root at protected/views/admin/processModels.php This patch will also be available in the follow-up point release
-
Greetings, We have been notified of a potential security vulnerability in X2Engine. This vulnerability will be fixed in the next release, but it is too important to wait until then. It affects all versions from 2.8 through 4.1.7. To patch/fix this vulnerability on your installation before the update: 1. Download the following archive: Security-Patch-Jul31-2014.tar.gz Or, if you're on 4.1.7, download the following package and proceed to step 4: Jul31-2014-4.1.7-security-patch.tar.gz 2. Unpack the archive 3. Find the archive file within the contents that corresponds to your version of X2En
-
Hi all, This release, which contains fixes to some rather serious bugs in 4.1.3, is going to be the last release we do before our next round of development. Currently this release is available only as a beta; it will be released to the broader userbase in a few days from now. X2Engine 4.1.4 (stable) is now available! To enable updating to beta versions, see the following section of the definitive guide to updating: http://wiki.x2engine.com/wiki/Software_Updates_and_Upgrades#Updating_to_Beta_Versions
-
Due to a bug in our deployment script that wasn't caught in our testing, the update data for 4.1.1 was not included, and this causes some rather serious post-update problems. We apologize for the inconvenience. If you are a user of Professional/Platinum Edition and updated earlier today or over the weekend, please contact us immediately for assistance. To all open source users: never fear; there are two ways to fix this. A. Reset the files to 4.1 and change the version in your configuration If you updated to 4.1.1 earlier today or over the weekend, your installation will have an incomplete l
-
Hello, This is release contains fixes to all of the very serious bugs that were pointed out in 4.0. Addendum: The update to 4.0.2 addresses a rather serious issue that came up in updates to 4.0.1 wherein if the adminstrative user name was not "admin", the user would lose administrator permissions. For information on how to recover from this error, see "Known Issues" on the X2Engine wiki. ---- GitHub Repository GitHub download link SourceForge download link X2Engine 4.0 Patch/follow-up release 4.0.1 (see CHANGELOG for full history) 3/31/2014 Fixed Bugs:1080: User Report1096: web tr
-
This is very close to the same as 3.7.4, but the bugs of 3.7.4 fixed. Download Links: GitHub X2Community SourceForge Fixed Bugs in this version:995: array_combine() [function.array-combine]: Both parameters should have at least 1 element996: file_get_contents(): Filename cannot be empty997: Property "Media.title" is not defined.998: CDbCommand failed to execute the SQL statement: SQLSTATE[HY093]: Invalid parameter number: parameter was not defined999: CDbCommand failed to execute the SQL statement: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax;
-
There is an issue in version 3.7.4 which prevents certain records from being viewed when logged in as a non-admin user. It can be fixed by downloading the file attached to this post and uploading it to replace the file protected/modules/docs/models/Docs.php. Docs.php
-
There is an issue that affects some servers* that is preventing software updates from working properly. It can be fixed by downloading the file attached to this post and uploading it to replace the file protected/components/UpdaterBehavior.php UpdaterBehavior.php * On affected servers, the php function http_build_query is unusually configured to use "&" as its query parameter separator, rather than "&". The patch is a work-around for this scenario.
