Archived

This topic is now archived and is closed to further replies.

  • 0

Fatal And Parse Error After Upgrade Pagelines

Question

Posted · Report post

Hi there, i just upgrade pagelines on 2 of 3 equal site (the difference is only the wp language)

This is the site:

http://aaabuyitaly.com

On Italian and English i receive 2 different error

On Russian nothing.

 

On English:

Parse error: syntax error, unexpected '*' in /home/aaabuyit/domains/aaabuyitaly.com/public_html/en/wp-content/themes/pagelines/includes/class.users.php on line 81

 

On Italian:

Fatal error: Cannot redeclare ploption() (previously declared in /home/aaabuyit/domains/aaabuyitaly.com/public_html/wp-content/themes/pagelines/includes/library.pagelines.php:26) in /home/aaabuyit/domains/aaabuyitaly.com/public_html/wp-content/themes/pagelines/includes/library.options.php on line 61

 

You can help me urgent please?

Share this post


Link to post
Share on other sites

9 answers to this question

Posted · Report post

On English site i have downgrade to 2.3.5 and now work but is not normal.. Italian is of line with the error.

Share this post


Link to post
Share on other sites

Posted · Report post

Now i have ugrade deactivating the plugin and reactivating and now work the english site  ?????

Which kind of error was:

Parse error: syntax error, unexpected '*' in /home/aaabuyit/domains/aaabuyitaly.com/public_html/en/wp-content/themes/pagelines/includes/class.users.php on line 81

 

Is it possible that the server.. lost packages and then the installation lost some script or something else?

Share this post


Link to post
Share on other sites

Posted · Report post

Stefano, the file class.users.php does not even have a line 81

 

Also library.pagelines.php does not have a line 26 in fact its only 4 lines long.

 

Looks like your wordpress upgrade failed? Try downloading the zip and uploading the files normally.

 

I can guarantee there is nothing wrong with the latest zip file.

Share this post


Link to post
Share on other sites

Posted · Report post

Stefano,  I've told you more than once to NOT USE the word "Urgent".  Your topics are no more urgent than anyone else's and will dealt with in proper order by our staff.  Such attention grabbing comments only make you look very bad to our moderators.   If I see it,  I'm going to remove the word URGENT and eventually, will be forced to moderate, if not suspend this account.

Share this post


Link to post
Share on other sites

Posted · Report post

Stefano,

 

It's possible your installation was corrupted, which is why those files are showing an errant " * " which breaks them.

 

Please don't reinstall everything.  That too can cause problems. 

 

You should however, log into your Launchpad account at http://pagelines.com/launchpad/member.php

 

Download PageLines (the latest version will be there). 

 

Unzip the folder to your Desktop.

 

FTP to your account.

 

Go to wp-content/themes/ and remove the pagelines folder.

 

Via FTP, upload the pagelines folder you unzipped to the Desktop. 

 

Login to your Dashboard.   Go and see if you get any errors.

Share this post


Link to post
Share on other sites

Posted · Report post

Let me know how it goes. I'm here for another two hours.

Share this post


Link to post
Share on other sites

Posted · Report post

All work... perfect!

I have to understand how validate the htlm for not receive anymore error.. the first time i used pagelines, i had  White House theme and i validate htlm and w3c with 25 plugin and all was perfect.. incredible.. now with 10 .. 933 error in the code... bah!

Share this post


Link to post
Share on other sites

Posted · Report post

Stefano, use this validator:  http://validator.w3.org/

 

If you're checking the whole site, then use the Validate by URI tab, but if you're validating your own HTML code, then copy it and paste it into the Validate by Direct Input tab.

 

Do the same thing with your CSS using this: http://jigsaw.w3.org/css-validator/

 

Glad that worked.

 

Most of those 933 errors are from the Less/Compiled process because the validator for CSS has not caught up with that technology. 

 

The best thing to do with CSS is to validate only your own custom code by Direct Input.

Share this post


Link to post
Share on other sites