May 4, 2011

xlm parse error: 0 (no error) | CyberSEO Pro | Support Forum

Avatar

Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_TopicIcon
xlm parse error: 0 (no error)
Topic Rating: 0 Topic Rating: 0 Topic Rating: 0 Topic Rating: 0 Topic Rating: 0 Topic Rating: 0 (0 votes) 
April 30, 2019
3:15 pm
Avatar
d-vino
Member
Members
Forum Posts: 10
Member Since:
April 30, 2019
sp_UserOfflineSmall Offline

Hi there,

I have two feeds which produce the same error (see above):

Login to see this link

Login to see this link

Both feeds are working properly in browser based RSS plug-ins...

What could be the issue?

Thanks,

Rolf

April 30, 2019
3:20 pm
Avatar
CyberSEO
Admin
Forum Posts: 3947
Member Since:
July 2, 2009
sp_UserOfflineSmall Offline

I can't see any problem wit these feeds. Just add them with the default settings.

April 30, 2019
4:20 pm
Avatar
d-vino
Member
Members
Forum Posts: 10
Member Since:
April 30, 2019
sp_UserOfflineSmall Offline

does not work.. how can I send a screenshot.. ?

April 30, 2019
4:59 pm
Avatar
d-vino
Member
Members
Forum Posts: 10
Member Since:
April 30, 2019
sp_UserOfflineSmall Offline

Hi there,

I would need serious support on this plugin.

On top of the error I mentioned above the plugin does not create posts (feeds are imported, however...).

At this point in time the plugin is totally not working for me.

How can that be? I am using the Avada Theme.

BR,

R.

April 30, 2019
5:44 pm
Avatar
CyberSEO
Admin
Forum Posts: 3947
Member Since:
July 2, 2009
sp_UserOfflineSmall Offline

Please email with login/password to the WordPress control panel of your site.

April 30, 2019
7:17 pm
Avatar
d-vino
Member
Members
Forum Posts: 10
Member Since:
April 30, 2019
sp_UserOfflineSmall Offline

What e-mail adress?

May 1, 2019
9:07 am
Avatar
CyberSEO
Admin
Forum Posts: 3947
Member Since:
July 2, 2009
sp_UserOfflineSmall Offline

The email is Login to see this link - just scroll the page down.

May 6, 2019
3:15 pm
Avatar
d-vino
Member
Members
Forum Posts: 10
Member Since:
April 30, 2019
sp_UserOfflineSmall Offline

Hi there, i'll take over the communication for our customer D-Vino.

The xml parse error: 0 (no error) occurs when i'd like to syndicate two RSS feeds: Login to see this link but they work perfectly with an RSS Reader, so they are definitely valid RSS feeds.

All other Feeds which i syndacte generate all the same "Syndicating RSS Feed... Fatal error: Maximum execution time of 9223372036854775807 seconds exceeded in ..."-Error, but randomly with different paths. I'll list some of the paths which occured in the fatal errors:

Path/wp-includes/wp-db.php Line 2007
Path/wp-content/plugins/cyberseo/cyberseo.php(52) : eval()'d code on line 3 
Path/wp-includes/wp-db.php on line 2245
Path/wp-includes/cache.php on line 120 

PHP Version of the hosting is 7.3 but i've also tested it with 7.2 and 7.1, doesn't changes anything. PHP max_execution_time is 720 seconds.

Nevertheless, some of the feeds still import posts. In my opinion it's not clear why those errors keep occurring though. There is no caching plugin activated and i've disabled those plugins which i thought could interfere. Unfortunately this didn't help either.

Do you still need the login for the website to check on this?

Best regards

Ramona

May 6, 2019
6:11 pm
Avatar
CyberSEO
Admin
Forum Posts: 3947
Member Since:
July 2, 2009
sp_UserOfflineSmall Offline

Login to see the quote

The feeds are valid. This is a PHP translator error and it is described in FAQ: Login to see this link

In almost all cases switching to PHP CGI mode solves the problem.

May 6, 2019
6:15 pm
Avatar
d-vino
Member
Members
Forum Posts: 10
Member Since:
April 30, 2019
sp_UserOfflineSmall Offline
10sp_Permalink sp_Print
0

Thanks for the reply.

I've already checked the FAQ and the answer you've quoted. The PHP mode is switched to CGI so this can't be a problem. I've also checked the 3rd party plugins and couldn't detect the problem there. Any other suggestions why this is happening?

And what about the two feeds mentioned above (those with the parse error: 0 (no error)) which don't get syndicated, any idea why this happens?

May 6, 2019
6:30 pm
Avatar
CyberSEO
Admin
Forum Posts: 3947
Member Since:
July 2, 2009
sp_UserOfflineSmall Offline
11sp_Permalink sp_Print
0

The error message is definitely related to the PHP engine (perhaps you need to update it along with MySQL server). As you can see by the error log it triggers in the WordPress code PHP related to MySQL every time when CyberSEO calls WordPress API Login to see this link function. So it just can't be fixed on CyberSEO side (it's being triggered by WordPress). I also had this issue on one of my own servers and fixed it by switching PHP to "CGI".

Now about the two feeds you can't pull. They are ok and I have pulled them at my test site w/o any problem (just like any other feeds). Seems there is something wrong with your CyberSEO feed settings. If you provide an access to your WordPress admin panel, I'll check them for you.

May 7, 2019
12:27 pm
Avatar
d-vino
Member
Members
Forum Posts: 10
Member Since:
April 30, 2019
sp_UserOfflineSmall Offline
12sp_Permalink sp_Print
0

I've checked back with the hoster and the hoster says the server is configured how the plugin recommends. 

The Fatal Error is solved btw, i think it had something to do with the open_basedir because there was nothing defined. I've changed that to {WEBSPACEROOT}{/}{:}{TMP}{/} and now the fatal error is gone. 

Unfortunately the parse error for the vinfolio rss feed still exists. I've installed the lite plugin and tried to syndicate both feeds with the light versions and the Login to see this link i get the parse error as well. (i have no idea why it worked with the light plugin but not with the prempium plugin)

Could you take another look?

May 7, 2019
12:37 pm
Avatar
CyberSEO
Admin
Forum Posts: 3947
Member Since:
July 2, 2009
sp_UserOfflineSmall Offline
13sp_Permalink sp_Print
0

Yes it is really configured according the plugin's requirement's but it is still crashes in the WordPress core code (not in CyberSEO). This means that something is missconfigured (wrong/buggy version of PHP, PHP libraries, MySQL server, Apache, Operating System etc).

Your hoster should understand that "Fatal error: Maximum execution time of 9223372036854775807 seconds exceeded in" can not be caused by the code. Course in case if it wasn't running for 2998651437 centuries. And it wasn't, right? I believe he understand that if the PHP engine fails with such a strange message, there is something definitely wrong with your hosting. If he is unable to fix it, I sincerely recommend you to find another hoster.

  1. Go to CyberSEO Pro -> Modification Tools
  2. Put the following two lines into the "PHP Code <?php .. ?>" box:
    echo file_get_contents("https://blog.vinfolio.com/feed");
    die();
  3. Click "Apply These Modifications To All Existing Posts"

The PHP will crash with the same error message.

May 7, 2019
8:14 pm
Avatar
d-vino
Member
Members
Forum Posts: 10
Member Since:
April 30, 2019
sp_UserOfflineSmall Offline
14sp_Permalink sp_Print
0

by the way.. it seems that if we install the CyberSEO light version of the plugin TOGETHER with the premium version... we can add feeds there.. and can still use them in the premium version... strange enough it seems to be possible to add feeds in the light version WITHOUT getting the parse and time limit errors...

May 7, 2019
8:22 pm
Avatar
CyberSEO
Admin
Forum Posts: 3947
Member Since:
July 2, 2009
sp_UserOfflineSmall Offline
15sp_Permalink sp_Print
0

This may depend from case to case. In my case on one server both plugins produce the same error if PHP works as Apache module. On other hosts everything works fine in any configuration.

Here is an edit. The newer versions of CyberSEO Pro and CyberSEO Lite have a little bit different data structure. CyberSEO Pro data arrays include objects, while CyberSEO Lite doesn't (that's because it doesn't use so many feed content types). As I said somewhere above, the error occurs every time when WordPress tries to save that data to the database via standard WordPress API update_option() function call.

I'll tell you more. When I was getting this error, it could be easily "fixed" by a simple restarting of Apache. After that everything was working absolutely normally. Once, twice.. and the issue has returned exactly on the 3rd time. That's why I'm absolutely sure it's a host-related problem.

Forum Timezone: Europe/Amsterdam

Most Users Ever Online: 541

Currently Online:
192 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

ninja321: 84

s.baryshev.aoasp: 68

Freedom: 61

Pandermos: 54

MediFormatica: 49

B8europe: 48

Member Stats:

Guest Posters: 337

Members: 2855

Moderators: 0

Admins: 1

Forum Stats:

Groups: 1

Forums: 5

Topics: 1641

Posts: 8353

Newest Members:

samuel2288, comercios.cercademi, wanmarkets, torontomark48, info.ckmedianetwork, contact.mybeautystar

Administrators: CyberSEO: 3947