Syntax error, unexpected T_NS_SEPARATOR

Question

Syntax error, unexpected T_NS_SEPARATOR

levycarneiro opened this issue 5 years ago · 23 comments

Ran into this issue when attempting to S/R a wordpress install (staging to www) via CLI.

wp_oauth_clients: 0 rows, 0 changes found, 0 updates made in 0.00028396 seconds
wp_oauth_refresh_tokens: replacing staging.community.newmessage.org with community.newmessage.org
wp_oauth_refresh_tokens: 0 rows, 0 changes found, 0 updates made in 0.00022697 seconds
wp_oauth_scopes: replacing staging.community.newmessage.org with community.newmessage.org
wp_oauth_scopes: 0 rows, 0 changes found, 0 updates made in 0.00022101 seconds
wp_options: replacing staging.community.newmessage.org with community.newmessage.org
syntax error, unexpected '\' (T_NS_SEPARATOR), expecting '{'
$

Any idea what could be wrong here?

Thanks!

Answer 1 · 2020-04-14T07:46:38.000Z

Same issue here; running 4.0.1

Answer 2 · 2020-04-14T10:04:49.000Z

what php version are you running? could you try with the last version on master?

Answer 3 · 2020-04-15T00:24:46.000Z

php 7.3.16
script v4.1
Mysql Ver 14.14 Distrib 5.7.29
issue happens only on wp_options table of wordpress.

Answer 4 · 2020-04-16T08:43:31.000Z

so it might be some serialised data, this tools tries to unserialise and there might be some error there. That's why you get that message, I cannot reproduce it on my side, can you post some sample?

Answer 5 · 2020-04-16T08:50:51.000Z

Well I think the issue comes from the Elementor plugin.

Answer 6 · 2020-04-16T08:54:15.000Z

thanks @dejury
some plugins don't play nice with our tool, @levycarneiro are you using the same plugin?

Answer 7 · 2020-04-16T14:07:35.000Z

Yes, with Elementor same error.
Error on option 'elementor_log'
Im simple remove this option from wp_options and problem is gone.
elementor_log in my case have 4kb length and not easy to undestand cause.

PS: A text variable affects script syntax? I'm scared...

Answer 8 · 2020-04-18T13:55:45.000Z

Indeed, we are using Elementor.

Answer 9 · 2020-04-20T09:04:57.000Z

Thanks for the report, some plugins don't play nice with SR and we cannot write specific code for each of them. Let's close this issue, if someone else is having the same problem, this page will pop up on search engines for sure.

Answer 10 · 2020-04-20T09:21:56.000Z

Well I'm not sure if that is the right decision. I agree that you should not have specific code for each and every plugin. But Elementor is a plugin that is so widely used, so I think for some plugins you have to make a decision to support it. For example the company that I work for uses Elementor in almost every site, and that are more then 200 sites. Which means we cannot use SR anymore?

Answer 11 · 2020-04-20T10:01:46.000Z

@dejury we don't use any of those plugins, you can fork SRDB and write your patches. Other developers already have forks for any sort of setup.

GPL software doesn't mean free stuff, you can study and change SRDB without limitations as long as you respect the license.

Happy Hacking

Answer 12 · 2020-05-09T23:53:57.000Z

@dejury
Ran into same issue today.
As an alternate manual solution, one can go in the admin panel under Elementor > Tools > Replace URL, and do the search and replace there for those sites. They have a dedicated helper tool to do that. That's what I did for my one case.

Answer 13 · 2020-05-16T09:53:24.000Z

I made a hacky patch for the unescaped \ in the elementor_log-option:
itg-dave@376591e

Answer 14 · 2020-06-25T09:40:22.000Z

I've seen this on a couple of our recent projects and we aren't using Elementor.

Works on all tables except wp_options. I plan on looking at this more closely soon so will report back.

Answer 15 · 2020-11-13T20:14:14.000Z

I have the issue in wp_usermeta – no Elementor in the project

Answer 16 · 2020-11-13T20:35:14.000Z

Can you identify the string that is causing the crash? It is it a really large blurb?

Answer 17 · 2020-11-13T20:44:34.000Z

No. I tried with extra verbose debug in CLI, but no usable details to isolate it. The table is semi big with 17 000 records (1.5 MB), but that shouldn't be a problem.

After I wrote I've tried several runs for debug and it appears that it actually does replace something, because the string was eventually changed in all recods.

Answer 18 · 2020-11-13T20:50:17.000Z

It might be a false sense of successful run as anything in the loop after that table was ignored. Have you tried the built in search and replace in the official wp cli? The feature actually exist there too, I usually try wpcli first.

Answer 19 · 2020-11-13T20:56:54.000Z

No, haven't tried the wp cli but I will - thx.

One possibly important detail I forgot to mention was that I actually changed from php 7.3.21 to 7.4.10 before the multiple runs that eventually made the replace. However, it still reported the error and stopped.

Som Googling on "'' (T_NS_SEPARATOR)" points to issues in the PHP code and possibly not the string it is trying to replace.

Answer 20 · 2020-11-13T21:03:57.000Z

No, it has to do with how the data was serialized in the db. The author of the plugin had made a comment about it. Anyways, good luck with wp cli. Let us know how it worked for you.

Answer 21 · 2020-11-14T05:41:42.000Z

I've got the same error stopped on wp_option table when used version 4.1.1 but all working when used older version 3.1.0 even there were PHP Notice info.

Answer 22 · 2021-01-07T21:36:16.000Z

@iwayanwirka thank you :) Your solution worked. Downloaded 3.1 from the repo and I am back in good hands. Wish I would have found this article sooner but I had to finally figure this out as it has plagued me for about 2 months now.

Answer 23 · 2022-02-15T20:35:29.000Z

This seems to be a duplicate. I've mentioned the solution here: #348