Jump to content


Photo

Wp Errors Suddenly: Warning: Creating Default Object From Empty Value In /homepages/5/d365318221/htdocs/wp-Content/themes/platformpro/core/library/cla

errors platformpro

Best Answer hop2us , 19 December 2012 - 09:51 PM

Hmmm. I talked to the hosting service and seems the were doing something with the upgrade of php. I think it's magically fixed now... Thanks Simon for your help!

Go to the full post


This topic has been archived. This means that you cannot reply to this topic.
5 replies to this topic

#1 hop2us

hop2us

    Advanced Member

  • Members
  • 64 posts

Posted 19 December 2012 - 07:30 PM

My site suddenly has a whole slew of errors at the top of the page and they all look like this:

 

Warning: Creating default object from empty value in /homepages/5/d365318221/htdocs/wp-content/themes/platformpro/core/library/class.layout.php on line 164

 

with different pages and php doc being affected. 

 

Originally there was an error saying the site needed to upgrade to php5 since the server was using php4 so I upgraded then got these errors. Any ideas?



#2 hop2us

hop2us

    Advanced Member

  • Members
  • 64 posts

Posted 19 December 2012 - 07:31 PM

I meant to attach a link to the site: http://lulusrescue.com



#3 Simon_P

Simon_P

    Messer

  • Administrators



  • 8388607 posts

Posted 19 December 2012 - 07:32 PM

Turn debugging off, should be off by default on all servers.



#4 hop2us

hop2us

    Advanced Member

  • Members
  • 64 posts

Posted 19 December 2012 - 07:37 PM

Sorry, how do I turn debugging off?



#5 Simon_P

Simon_P

    Messer

  • Administrators



  • 8388607 posts

Posted 19 December 2012 - 07:45 PM

Well that depends on your host.

Sometimes its as easy as adding something to .htaccess file, but you need to ask them as it should be off by default.



#6 hop2us

hop2us

    Advanced Member

  • Members
  • 64 posts

Posted 19 December 2012 - 09:51 PM   Best Answer

Hmmm. I talked to the hosting service and seems the were doing something with the upgrade of php. I think it's magically fixed now... Thanks Simon for your help!