Honestly doubt that would be seen in 2.1.... and possibly not ever. It really depends on how much they want to expand their ecosystem.Not least whether portalisation and blogs might ever be official products.
I noticed there are a couple places where a user's secret_key is pushed into the cache which causes "fun" with JSON. And changing content_type to varbinary can potential mean it will contain invalid-unicode sequences when developers try to interact with it as a string at various levels.That said, we are generally making more use of JSON albeit encoded/decoded in PHP and still stored in BLOBs in MySQL. We'd recommend that, where practicable, developers use JSON for new fields rather than PHP serialization and if it's sane to do so, update existing fields to store JSON. We haven't routinely done that everywhere, but if you can it will be worth doing.
its admin demo update to XF2?
The demo should host the latest stable version because it is for the potential customers to allow them try the product that they would buy.its admin demo update to XF2?
My test server has mySQL 5.1 which does not allow the upgrade to happen until we update to mySQL 5.5We've bumped up the minimum requirements for MySQL to 5.5 but not stretched them far enough to use the native JSON support.
That said, we are generally making more use of JSON albeit encoded/decoded in PHP and still stored in BLOBs in MySQL. We'd recommend that, where practicable, developers use JSON for new fields rather than PHP serialization and if it's sane to do so, update existing fields to store JSON. We haven't routinely done that everywhere, but if you can it will be worth doing.
Is there anyway we can revert/stop the update?
$ sudo apt-get install mysql-server-5.5
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package mysql-server-5.5
$ sudo apt-get install mysql-server-5.6
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Couldn't find package mysql-server-5.6
$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Points taken. I actually have a new server set up to move this to. May as well take the time and do it.You know, wiping and reinstalling would give you a fresh OS too ... with news repos, new mariadb, php 7, etc.etc.
If you need some linux help (other than "I want to continue with my hacked server"), gladly, but we should go into a new thread.
Perfect. uploaded the latest xf 1.5.x files on top got it back to where it was. Thanks Chris.Certainly not the correct thread for further discussion of the issue, though certainly welcome to continue it elsewhere.
Indeed just reverting the files from a backup, or even just downloading the same version of XF 1.X you had and uploading those files should sort it too.
We've bumped up the minimum requirements for MySQL to 5.5 but not stretched them far enough to use the native JSON support.
That said, we are generally making more use of JSON albeit encoded/decoded in PHP and still stored in BLOBs in MySQL. We'd recommend that, where practicable, developers use JSON for new fields rather than PHP serialization and if it's sane to do so, update existing fields to store JSON. We haven't routinely done that everywhere, but if you can it will be worth doing.
We use essential cookies to make this site work, and optional cookies to enhance your experience.