Archived

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

  • 0

Moving pagelines Site

Question

Posted · Report post

Hi,

 

I'm trying to move a Wordpress site with pagelines pro theme from a subdomain to a subdirectory (/wp) of the same domain, so everything on the same server. I'm following the instructions given here: http://codex.wordpress.org/Moving_WordPress

I'm now at point 9 of: "When Your Domain Name or URLs Change">"On Your Existing Server": I have changed the Wordpress address and the Site address in Wordpress setting>general, and copied all the files to the new directory. Now, when I'm trying to connect to http://www.mydomain.com/wp/wp-admin/, I get one of the following three errors for every pagelines section:

 

Warning: is_file() [function.is-file]: open_basedir restriction in effect. File(/home/httpd/vhosts/mydomain.com/subdomains/wordpress/httpdocs/wp-content/themes/pagelines/sections/boxes/section.php) is not within the allowed path(s): (/home/httpd/vhosts/mydomain.com/httpdocs:/tmp:/usr/share/pear) in /home/httpd/vhosts/mydomain.com/httpdocs/wp/wp-content/themes/pagelines/includes/class.register.php on line 130

 

Warning: is_file() [function.is-file]: open_basedir restriction in effect. File(/home/httpd/vhosts/mydomain.com/subdomains/wordpress/httpdocs/wp-content/plugins/pagelines-sections/pagelines-soapbox/section.php) is not within the allowed path(s): (/home/httpd/vhosts/mydomain.com/httpdocs:/tmp:/usr/share/pear) in /home/httpd/vhosts/mydomain.com/httpdocs/wp/wp-content/themes/pagelines/includes/class.register.php on line 135


Warning: is_file() [function.is-file]: open_basedir restriction in effect. File(/home/httpd/vhosts/mydomain.com/subdomains/wordpress/httpdocs/wp-content/plugins/pagelines-sections/fittext-section/section.php) is not within the allowed path(s): (/home/httpd/vhosts/mydomain.com/httpdocs:/tmp:/usr/share/pear) in /home/httpd/vhosts/mydomain.com/httpdocs/wp/wp-content/themes/pagelines/includes/class.register.php on line 140

 

 

and only ONE other error:

 

Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/mydomain.com/httpdocs/wp/wp-content/themes/pagelines/includes/class.register.php:140) in/home/httpd/vhosts/mydomain.com/httpdocs/wp/wp-includes/pluggable.php on line 876

 

 

It seems, page lines has stored URLs of the sections somewhere and is still referencing to this, but I don't find anything relevant in the database.

 

What to do?

Share this post


Link to post
Share on other sites

11 answers to this question

Posted · Report post

How should I go to the store page? I don't see anything apart from the error messages.

Share this post


Link to post
Share on other sites

Posted · Report post

I thought you said you turned off error logging?

Share this post


Link to post
Share on other sites

Posted · Report post

Yes, I turned off log_errors  in the PHP settings of the server.

Did you mean to turn off display_errors  ?

Share this post


Link to post
Share on other sites

Posted · Report post

As i said before, a production server should not show any php errors by default, thats what WP_DEBUG setting does in wp-config.php, it turns them all on so you can debug plugins themes etc.

Share this post


Link to post
Share on other sites

Posted · Report post

Catrina,

 

I don't think this is it. To modify the open_basedir settings will not change the fact that class.register.php is looking for the sections in the subdomain where they aren't anymore. So these URLs must be stored somewhere and can hopefully be adjusted, but where?

Share this post


Link to post
Share on other sites

Posted · Report post

Go to /wp-admin/admin.php?page=pagelines_extend it will rebuild the sections caches.

Share this post


Link to post
Share on other sites

Posted · Report post

Unfortunately this gives the exact same errors.

I suppose for this to work I would have to be logged in, but I don't get that far.

Share this post


Link to post
Share on other sites

Posted · Report post

Yes you would have to be logged in, of couse you could just turn off error logging, should be off anyway on a production server.

Share this post


Link to post
Share on other sites

Posted · Report post

OK, I managed to log-in. Then I get the following errors in addition to the ones mentioned above:

 


Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/smv.ch/httpdocs/wp/wp-content/themes/pagelines/includes/class.register.php:140) in/home/httpd/vhosts/smv.ch/httpdocs/wp/wp-login.php on line 368

Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/smv.ch/httpdocs/wp/wp-content/themes/pagelines/includes/class.register.php:140) in/home/httpd/vhosts/smv.ch/httpdocs/wp/wp-login.php on line 380

Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/smv.ch/httpdocs/wp/wp-content/themes/pagelines/includes/class.register.php:140) in/home/httpd/vhosts/smv.ch/httpdocs/wp/wp-includes/pluggable.php on line 680

Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/smv.ch/httpdocs/wp/wp-content/themes/pagelines/includes/class.register.php:140) in/home/httpd/vhosts/smv.ch/httpdocs/wp/wp-includes/pluggable.php on line 681

Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/smv.ch/httpdocs/wp/wp-content/themes/pagelines/includes/class.register.php:140) in/home/httpd/vhosts/smv.ch/httpdocs/wp/wp-includes/pluggable.php on line 682

Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/smv.ch/httpdocs/wp/wp-content/themes/pagelines/includes/class.register.php:140) in/home/httpd/vhosts/smv.ch/httpdocs/wp/wp-includes/pluggable.php on line 876

 

 

If I go to /wp-admin/admin.php?page=pagelines_extend, as you suggested; i get the same errors as in my first post. And that's the only thing displayed.

 

I have now turned error logging off and emptied the cache. The result is still the same. What to do?

Share this post


Link to post
Share on other sites

Posted · Report post

OK so go to the store page and click the blue refresh button.

Share this post


Link to post
Share on other sites