0
Welcome Guest! Login
0 items Join Now

Fatal Error

    • Sean Ryan's Avatar
    • Sean Ryan
    • Jr. Rocketeer
    • Posts: 26
    • Thanks: 0

    Fatal Error

    Posted 11 years 8 months ago
    • Hi,
      I received the following error when trying to access the global config and any custom HTML of my site 217.115.114.152/~klassic2 .
      I am a rocket theme subscriber but this template was purchased from Theme Forrest and not getting much response from the developer.
      Any help would be greatly appreciated.

      Regards

      Sean

      Edit: Just discovered disabling roksproket has solved the issue
    • DanG's Avatar
    • DanG
    • Preeminent Rocketeer
    • Posts: 36750
    • Thanks: 3229
    • Custom work done

    Re: Fatal Error

    Posted 11 years 8 months ago
    • After a few seconds on that site without doing anything, this page loads:
      This image is hidden for guests.
      Please log in or register to see it.

      I tried Chrome, Firefox and IE9 with the same result.
    • Sean Ryan's Avatar
    • Sean Ryan
    • Jr. Rocketeer
    • Posts: 26
    • Thanks: 0

    Re: Fatal Error

    Posted 11 years 8 months ago
    • Yes Dan but I am not sure whats happening....there is certainly some conflict with a module or plugin. If unpublish all plugins then the home page loads. However I do not know how to easily identify with plugin is causing the issue. I have deleted the site and started again so lets see what happens.

      Cheers

      Sean
    • DanG's Avatar
    • DanG
    • Preeminent Rocketeer
    • Posts: 36750
    • Thanks: 3229
    • Custom work done

    Re: Fatal Error

    Posted 11 years 8 months ago
    • Sean Ryan wrote:
      Yes Dan but I am not sure whats happening....there is certainly some conflict with a module or plugin. If unpublish all plugins then the home page loads. However I do not know how to easily identify with plugin is causing the issue. I have deleted the site and started again so lets see what happens.

      Cheers

      Sean
      Ouch!!!
      My recommended approach to this is to create a test DB. Then use Akeeba Backup to clone the site to a subfolder of the root. Restore the clone using the test DB and then start dropping plugins and extensions till you find the culprit.
    • prim's Avatar
    • prim
    • Preeminent Rocketeer
    • Posts: 17290
    • Thanks: 217

    Re: Fatal Error

    Posted 11 years 8 months ago
    • Hmm ok, so we can mark this as solved?
    • Please reply with a direct link to the issue & create a new thread for each new issue.

      A template is only as good as the content that goes into it ;) - DanG
    • DanG's Avatar
    • DanG
    • Preeminent Rocketeer
    • Posts: 36750
    • Thanks: 3229
    • Custom work done

    Re: Fatal Error

    Posted 11 years 8 months ago
    • Hi Sean
      First thing I found was a biggie, Admin -> Extension Manager -> Warnings
      The value of the upload_max_filesize in the php.ini file is greater than the post_max_size variable. The post_max_size variable will take precedence here and block requests larger than it. This is generally a server misconfiguration when trying to increase upload sizes. Please increase the upload_max_filesize to at least match the post_max_size variable or vice versa

      Editing the php.ini file (recommended)
      For Linux Web Hosting and Dedicated Website Servers running PHP as a CGI
      Every installation of PHP has a default or global php.ini file for the default PHP settings. Normally it is suggested to leave the default or global php.ini file unaltered and to simply create your own php.ini file wherever needed to override the default settings. You can create the php.ini file using a text editor and saving the file to the folder where the settings should apply. Please note that using a php.ini file to override the default settings will only alter the PHP settings for all PHP files in the directory where it is saved. This means that any PHP files in subfolders will not recognize the changes you've made in the php.ini file. You will have to copy the file to any subdirectories needed.
      Write each directive along with its value on separate lines. Lines starting with a hash symbol (#) are comment lines and have no effect on the settings within the file.
      An example:
      memory_limit = 64M
      upload_max_filesize = 10M
      post_max_size = 12M

      Editing the .htaccess file
      For Dedicated Website and Linux Root Servers where PHP is running as an Apache module.
      The .htaccess file is used to set Apache Web Server settings but can also be used to set php directives when used as a module. The settings in .htaccess file are recursive meaning that the settings within the .htaccess file will apply to all PHP files within the directory where it is saved as well as subdirectories. There is no default .htaccess file be default unless one was included with a Web Application install (such as Joomla, Wordpress, etc.) If not already created, you will have to create the .htaccess file using a text editor and save the file to the folder where the settings need to be applied. Please note that the dot(.) preceding the .htaccess file signifies it as a hidden file.
      Write each directive along with its value on separate lines. Lines starting with a hash symbol (#) are comment lines and have no effect on the settings within the file.
      An example:
      php_value memory_limit "64M"
      php_value upload_max_filesize "10M"
      php_value post_max_size "12M"

      Some hosters offer you the ability to change your php settings in the Cpanel or Plesk panel for your account, such as HostGator:
      Making Changes via cPanel's php.ini QuickConfig utility in the "Software/Services" section of your cPanel.
      1.Login to cPanel.
      2.Click on php.ini QuickConfig in the "Software/Services" section.
      3.Enable QuickConfig if not already enabled.
      4.Change the settings that you want to change.
      5.Click the Save Changes button to save your changes.

      Once that's fixed we'll go from there.

Time to create page: 0.070 seconds