Jump to content

Recommended Posts

BBX

Have no clue how to handle this error and would appreciate any help :

"Fatal error: Uncaught exception 'UnexpectedValueException' with message 'RecursiveDirectoryIterator::__construct(/home/bbx/public_html/wp-content/plugins/pagelines-sections/twin-shot/libs/scroll) [<a href='recursivedirectoryiterator.--construct'>recursivedirectoryiterator.--construct</a>]: failed to open dir: Too many open files' in /home/bbx/public_html/wp-content/themes/pagelines/includes/class.register.php:177 Stack trace: #0 [internal function]: RecursiveDirectoryIterator->__construct('/home/bbx/publi...') #1 /home/bbx/public_html/wp-content/themes/pagelines/includes/class.register.php(177): RecursiveDirectoryIterator->getChildren() #2 /home/bbx/public_html/wp-content/themes/pagelines/includes/class.register.php(62): PageLinesRegister->pagelines_getsections('/home/bbx/publi...', 'child') #3 /home/bbx/public_html/wp-content/themes/pagelines/includes/init.php(221): PageLinesRegister->pagelines_register_sections() #4 /home/bbx/public_html/wp-content/themes/pagelines/functions.php(22): require_once('/home/bbx/publi...') # in /home/bbx/public_html/wp-content/themes/pagelines/includes/class.register.php on line 177?

Have not added any new files and was wondering if it has got to do with not upgrading Pagelines when wordpress upgrade to the latest version?

Share this post


Link to post
Share on other sites
Simon

I think this is because certain files permissions have changed. Make sure all files under the pagelines folder is readable by the web server. You should upgrade anyway you have an old version.

Always update themes/plugins BEFORE updating wordpress. It tells you on the updates page.

Share this post


Link to post
Share on other sites
BBX

Thanks Simon_P for responding.

The matter is now resolved and caused by the new Pagelines Framework update. I have restored the backups and then upload the new version into cpanel. The problem no longer exist.

Cheers,

Pauline :D;)

Share this post


Link to post
Share on other sites
James B

Thanks for letting us know Pauline. I'm glad you got it sorted :-)


Kindly search the forum and read the documentation before posting. It will help you resolve many issues.

For CSS help be sure to check out W3Schools first and be sure to download FireBug for FireFox for troubleshooting.

James B

Share this post


Link to post
Share on other sites
James B

The topic was marked as resolved.


Kindly search the forum and read the documentation before posting. It will help you resolve many issues.

For CSS help be sure to check out W3Schools first and be sure to download FireBug for FireFox for troubleshooting.

James B

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

    • dbrowne02
      By dbrowne02+
      Hey, this looks like a great product. Thank you for making it!
      Unfortunately, when I activated plugin, I got this error. Thanks in advance for helping with this. 

      Fatal error: Cannot redeclare wmHtmlEditorEnable() (previously declared in /home/dbrowne02/brownelaborlaw.com/wp-content/plugins/enhanced-options-editor/enhanced-options-editor.php:14) in /home/dbrowne02/brownelaborlaw.com/wp-content/plugins/enhanced-options-editor/enhanced-options-editor.php on line 15
    • pillar
      By pillar
      After preview OR activation of the Bespoke Theme 1.0.1 an internal error 500 occurs. Wp debug states: Fatal error: Cannot redeclare class EditorStoreFront in /var/www/[...]/wp-content/themes/jg-bespoke/dms/editor/editor.api.php on line 7.
       
      This happen on a clean webserver (Ubuntu 14.04 LTS server 64bit, Apache/2.4.7 (Ubuntu), MySQL5.5.40-0ubuntu0.14.04.1, PHP 5.5.9-1ubuntu4.5, Wordpress 4.0) and neither
      Wordpress plugins are installed nor .htaccess files are placed.
       
      Can anybody help me?
       
    • gsquared
      By gsquared
      For some reason, when I go to the home page of my client's site, it's showing the following error:
       
      Fatal error: Call to undefined function setup_pagelines_template() in /home/p1sivng/public_html/wp-content/themes/pagelines/page.alpha.php on line 24
       
      I tried disabling other plugins, but that didn't help. I changed enabled debug mode, but it didn't display any additional information.
       
      In the error log, it's showing the following line:
       
      PHP Fatal error:  Call to undefined function setup_pagelines_template() in /home/p1sivng/public_html/wp-content/themes/pagelines/index.php on line 50
       
      I am using PageLines Framework version 2.4.5
      Wordpress version 4.0
       
      The URL is: http://www.printadvertisingusa.com
       
      Any ideas what this could be?
       
      Gary
    • nfp1900
      By nfp1900
      Hi
       
      I'm really looking for some help from all those WP users out there as I've hit a bit of brick wall elsewhere. I built this site www.delada.net with no issues but a couple of days ago I started getting "Plugin could not be activated because it triggered a fatal error"  but no other error messages. If I update an active plugin it updates then fails to reactivate. There are a bunch of inactive plugins (from the previous developer - around 25) but only 6 are active on this site and it's nothing I haven't got on other installations. 
       
      I've built and updated  30+ wordpress sites with every version of pagelines right up to this DMS 2.0.4 version and I've never seen this before. I called the host Godaddy which the client already had in place (it wasn't my choice) and they simply said they don't support Wordpress so that wasn't such a good start. 
       
      Anyone got any bright ideas about what to do? The WP forums haven't turned up anything or a reply. Only thing I see is that there is a plugin nonce error on activation which points to an incorrect authentication key (maybe?).
       
       
       
       
×