Announcement

Collapse
No announcement yet.

Fatal Error upgrading from 1.5.7 to 1.5.8 Non-unique widget GUID

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Fatal Error upgrading from 1.5.7 to 1.5.8 Non-unique widget GUID

    I'm upgrading from 5.1.7 to 5.1.8

    The upgrading process is not being completed, i get this Fatal errorr message:

    final Step #4
    Fatal Error Occurred
    Non-unique widget GUID: "vbulletin-widget_search-4eb423cfd6a5f3.08329785" on /home/myuser/public_html/core/vb/xml/import/widget.php : 62


    Any suggestion?
    Any help on this would be appreciated.


    Server Type Linux
    Web Server Apache v2.4.12 (cgi-fcgi)
    PHP 5.5.26
    MySQL Version 10.0.20-MariaDB

  • #2
    Hi,
    Can you help with this? I have that same problem.
    Joomla Turkey - http://www.joomlatr.org

    Comment


    • #3
      For those of you having the same problem.

      How to fix it:


      1) Check the error message and select the last digits for execute a query, for example, my message was this:

      Non-unique widget GUID: "vbulletin-widget_search-4eb423cfd6a5f3.08329785" on /home/myuser/public_html/core/vb/xml/import/widget.php : 62

      So I selected the last 8 digits for the query.

      2) Using phpMyadmin or mysql command execute this:

      Code:
      select * from widget where guid like '%08329785%';


      (replace the digits for your owns)

      Check the query results and put attention on the widgetid


      For example: 308 , 309, 310
      3) Then, simply delete them using phpMyadmin

      Or if you are using mysql command, you can do the following:


      SELECT * FROM widgetinstance WHERE widgetid IN (308,309,310)

      If it returns any result, then run the following:

      DELETE FROM widgetinstance WHERE widgetid IN (308,309,310)

      Then, whether the first query returned results or not, run the following:

      DELETE FROM widget WHERE category='customized_copy'

      Please make a database backup before doing this.
      Obviously you should replace "308,309,310" in the first two queries with your own IDs of your custom modules.


      4) Run the upgrade process again

      Comment

      Related Topics

      Collapse

      Working...
      X