Tagged: 

Viewing 7 reply threads
  • Author
    Posts
    • #6725

      Just installed the update 0.9.9.8 => error 500 on the backend / white page
      WP_DEBUG is ON but I can’t debug it, it stays white 🙁

      Seems like the same problem as this guy, I also have Avada:
      https://wordpress.org/support/topic/piklist-doesnt-play-nice-with-avada-theme-with-fusion-core?replies=12

      Is there any chance I could get the old version back? Could someone provide a link maybe?
      https://wordpress.org/plugins/piklist/

      
      Avada Versions: 
      
      ### Avada Versions ###
      
      Current Version: 4.0.3
      Previous Version: 3.9.3  4.0  4.0.1  4.0.2
      : Run Manual Migration From Version 4.0.2 to Version 4.0
      
      ### WordPress Environment ###
      
      Home URL: http://wp.andanza.de
      Site URL: http://wp.andanza.de
      WP Version: 4.5.2
      WP Multisite: –
      WP Memory Limit: 256 MB
      WP Debug Mode: ✔
      Language: en_US
      
      ### Server Environment ###
      
      Server Info: Apache
      PHP Version: 5.6.22
      PHP Post Max Size: 72 MB
      PHP Time Limit: 30 - We recommend setting max execution time to at least 180.  To import classic demo content
      300 seconds of max execution time is required.See: Increasing max execution to PHP
      
      PHP Max Input Vars: 1000 - Recommended Value: 1584.Max input vars limitation will truncate POST data such as menus. See: Increasing max input vars limit.
      SUHOSIN Installed: –
      ZipArchive: ✔
      MySQL Version: 5.5.47
      Max Upload Size: 70 MB
      DOMDocument: ✔
      WP Remote Get: ✔
      WP Remote Post: ✔
      GD Library: bundled (2.1.0 compatible)
      
      ### Active Plugins (24) ###
      
      Enable Media Replace: by Måns Jonasson
      Favicon by RealFaviconGenerator: by Philippe Bernard
      Fusion Core: by ThemeFusion
      Image Map Pro: by Nikolay Dyankov
      Quform: by ThemeCatcher
      MainWP Child: by MainWP
      Passwordless Login: by Cozmoslabs
      sareiodata
      
      Profile Builder - Custom CSS Classes on fields: by cozmoslabs
      Madalin Ungureanu
      
      Profile Builder - Custom Profile Menus Add-On: by Cozmoslabs
      Cristophor Hurduban
      
      Profile Builder - Email Confirmation Field: by Cozmoslabs
      Adrian Spiac
      
      Profile Builder - Labels Edit Add-On: by Cozmoslabs
      Cristophor Hurduban
      
      Profile Builder - Placeholder Labels Add-On: by Cozmoslabs
      Cristophor Hurduban
      
      Profile Builder - Social Connect Add-On: by Cozmoslabs
      Madalin Ungureanu
      Cristophor Hurduban
      
      Profile Builder - Multiple Admin E-mails Add-On: by Cozmoslabs
      Mihai Iova
      
      Profile Builder Pro: by Cozmoslabs
      Madalin Ungureanu
      Antohe Cristian
      Barina Gabriel
      Mihai Iova
      
      Slider Revolution: by ThemePunch
      Server IP & Memory Usage Display: by Apasionados
      Apasionados del Marketing
      
      ShortPixel Image Optimizer: by ShortPixel
      WPML Multilingual CMS: by OnTheGoSystems
      UpdraftPlus - Backup/Restore: by UpdraftPlus.Com
      DavidAnderson
      
      WP Editor: by Benjamin Rojas
      WPML Sticky Links: by OnTheGoSystems
      WPML String Translation: by OnTheGoSystems
      
    • #6726
      Steve
      Keymaster

      @pressworthammer– Seems to be an issue with the commit. Please delete the entire plugin folder via FTP and then go to Plugins > Add New to install.

      Sorry about any inconvenience.

    • #6727

      Thanks a lot for the super quick response – problem solved with your advice!

    • #6728
      jphickey
      Member

      i experienced the same and reported via comment on the site. I deleted and reinstalled 9.9.98 and things seem alright again. I’ve got several sites, and chance a fix/upgrade can save me from having to conduct this process at each of the sites. If not, I’ll take a link to the former version and wait for the next upgrade if indeed I should not expect same issue then. Your assistance is appreciated even though I primarily use the product for the Helpers at the current time.

    • #6729
      Steve
      Keymaster

      @jphickey– It should update as normal now. We had an issue with our commit to WordPress.org.

      You should nave no issues now.

    • #6747
      ruby
      Member

      I have the same problem (blank page w/ HTTP 500 Internal Server Error).

      However, I don’t use WordPress’s FTP feature. I deleted the old plugin via command line and then got the new version using wget.

      After I enable the plugin, http://mywordpress_website_FQDN/wp-admin becomes inaccessible (until I delete entire Piklist plugin folder).

      Can you please advise?

      Thanks,

    • #6748
      ruby
      Member

      While I was waiting for feedback to this (HTTP 500 Internal Server Error) inquiry…

      I had been seeing the following “PHP Fatal error” a lot in /var/log/http/error_log.
      “PHP Fatal error: Call to undefined function mb_strtolower() in
      /var/www/html/wp-content/plugins/piklist/includes/class-piklist.php on line 1228”

      So I installed mbstring (per WordPress’s instructions below) and restarted httpd.
      https://wordpress.org/support/topic/fatal-error-call-to-undefined-function-mb_strtolower

      Yum updated the following packages and now I’m able to access my WP-ADMIN page again (No more HTTP 500 errors).

      Jun 19 03:31:22 ip-xxx-xxx-xxx-xxx yum[31466]: Updated: php-common-5.4.16-36.1.el7_2.1.x86_64
      Jun 19 03:31:23 ip-xxx-xxx-xxx-xxx yum[31466]: Updated: php-cli-5.4.16-36.1.el7_2.1.x86_64
      Jun 19 03:31:23 ip-xxx-xxx-xxx-xxx yum[31466]: Updated: php-pdo-5.4.16-36.1.el7_2.1.x86_64
      Jun 19 03:31:23 ip-xxx-xxx-xxx-xxx yum[31466]: Updated: php-mysql-5.4.16-36.1.el7_2.1.x86_64
      Jun 19 03:31:23 ip-xxx-xxx-xxx-xxx yum[31466]: Updated: php-5.4.16-36.1.el7_2.1.x86_64
      Jun 19 03:31:23 ip-xxx-xxx-xxx-xxx yum[31466]: Installed: php-mbstring-5.4.16-36.1.el7_2.1.x86_64

    • #6753
      Steve
      Keymaster

      @ruby– Great! Glad you got it working. Closing ticket.

Viewing 7 reply threads
  • The topic ‘Error 500 on backend after update’ is closed to new replies.