Check this out:
Replaced last version by 1.2 beta deleting and uploading to plugins folder.
Parse error: syntax error, unexpected T_OBJECT_OPERATOR in plugins/polylang/polylang.php on line 154
Plugin Author
Chouby
(@chouby)
Thank you for testing. Maybe I am using some functionality not available in your PHP version. What is it?
Could you try to replace in polylang/polylang.php @ line 153
if (version_compare($options['version'], POLYLANG_VERSION, '<'))
(new PLL_Upgrade($options))->upgrade_at_activation();
by
if (version_compare($options['version'], POLYLANG_VERSION, '<')) {
$upgrade = new PLL_Upgrade($options);
$upgrade->upgrade_at_activation();
}
EDIT: if the error is removed by the correction above, then you will get several other errors as I use this syntax several times. IF you confirm I found the right correction, I’ll upload a new version tomorrow
Using PHP version 5.2.17
Looks like the fix works, but same issue at line 233
Hi, I have an issue with the polylang plugin,
I install it and activate it but when I press on the menu it gives me apologize page not found.
I did all the steps and still didn’t find a solution to the certain issue
Plugin Author
Chouby
(@chouby)
@miguelcortereal
I installed PHP 5.2.4 which is the minimum requested by WP and reproduced the same errors (it seems that the syntax I used was introduced with PHP 5.4). Hopefully I modified all lines where I used this syntax. I just uploaded a new version at same link. Thanks again for testing. It helps a lot.
@effoua
Do you mean it worked with Polylang 1.1.5 and no more with 1.2beta?
unexpected T_OBJECT_OPERATOR error is gone, it runs now.
The next issue I’ve noticed is that all synchronization of menus, posts, pages, taxonomies and strings table is lost.
Not sure if this was triggered by the previous error that eventually made run only partially the upgrade routine.
@chouby
I downloaded Polylang Version 1.1.5 and I have this issue
If you can help me I will appriciate it I am trying to see the issue for several days now and I dont find any solution
@ effoua
Try this:
Go to WP Settings menu, select permalinks and press save changes.
If it keeps returning Page not found, check your menu(s) links at Appearance -> Menus.
And there’s also this:
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, ‘Array’ was given in /wp-includes/plugin.php on line 173
Sorry, forget about previous post warning, it’s something else.
Plugin Author
Chouby
(@chouby)
@miguelcortereal
The upgrade procedure has not run because I made a mistake in versions numbers 🙁
Currently the version number stored in your database should be 1.2dev42. To run the upgrade:
You have first to change 1.2dev40 to 1.2dev43 in:
include/upgrade.php @ line 90
And second change 1.2dev42 to 1.2dev43 in:
polylang.php @ line 5 and @ line 42
Then you run WordPress and the upgrade of your database should run.
@effoua
If the solution proposed by @miguelcortereal does not work, please open a new thread as I prefer to keep this one for 1.2beta bugs reports (otherwhise we will mix everything).
Now 1.2 beta is running. I did make sure that after the last files revision (the version numbers) the plugin would deactivate and activate, so that database upgrade could run.
1) Assuming it ran, I still don’t have the previous settings, this means all synchronization is lost and tables strings as well.
Polylang Settings is showing this:
” There are posts, pages, categories or tags without language set. Do you want to set them all to default language ? “
Checking this option and saving the settings doesn’t change anything and it keeps there.
2) Flags don’t show anywhere.
I have the option to revert the database for yesterday’s backup position I did before running beta version.
If you think that would be useful to make run again the upgrade, I can arrange that.
Plugin Author
Chouby
(@chouby)
I feel dumb. I made a lot of upgrade tests and then made a modification which disabled the ugrade 🙁 And the modifications I asked you to do are not sufficient to make upgrade working again.
The best now is in fact that you revert to the database when 1.1.5 was activated and that you upgrade to latest 1.2beta. I uploaded again a new version (named 1.2dev43) which hopefully will run smoothly (I just tested it again).
Reverted the database for the position of 1.1.5 and the plugin as well to confirm everything looked as before.
Strangely the flags persist to not display anywhere, I recall that the missing flags issue only came after running 1.2 beta version.
Plugin Author
Chouby
(@chouby)
Do you mean that the flags don’t display on 1.1.5? Both on admin and frontend?
