0
Welcome Guest! Login
0 items Join Now

Ugh. My whole site is toast - accidentally turned off a Rok

    • Sleeper's Avatar
    • Sleeper
    • Rocketeer
    • Posts: 55
    • Thanks: 0

    Ugh. My whole site is toast - accidentally turned off a Rok

    Posted 11 years 5 months ago
    • I had this $@^%$^#^#ing error:

      Error loading component: com_tags, Component not found

      So I was disabling extensions to see if one of them might be causing it. (Trust me, I have Googled the living heck out of this, and NONE of the proposed solutions work! I upgraded to version 3.2 and the wheels came off my site - I AM SO MAD!)

      In any case, I disabled something central to the site - I don't know whether it was RokSprocket or RokCommon, but it trashed my whole site instantly when I disabled it. So I went into the database via phpMyAdmin and enabled all of the Rok extensions again. The site came back - but now the cache fails for no apparent reason.

      So if you load a page it loads OK and looks fine, but if you refresh the page or click the same link again - *poof* - it is a white page that looks like garbage.

      colleenlodge.com

      try loading, and then refreshing.

      And on top of that, that $^$@##$ing error message about tags still exists, with no hope in sight!

      I really really really really really hope someone can help. This is one of the worst messes I have ever been in, and I have been doing this for 14 years.
    • MrT's Avatar
    • MrT
    • Preeminent Rocketeer
    • Posts: 101084
    • Thanks: 13484
    • Web Designer/Developer

    Re: Ugh. My whole site is toast - accidentally turned off a Rok

    Posted 11 years 5 months ago
    • You did take a backup before you upgraded - right? you should always take a backup before upgrading anything (akeeba backup recommended).

      J3.2 has lots of bugs in it - so It's not recommended to upgrade to it for production use yet.

      But I guess you didn't take a backup and now can't go back, so the only way is forward...

      1. extensions manager > database > FIX button - should fix the tags error
      2. reinstall roksprocket extensions
      3. clear server cache - system > clear cache - tick all - DELETE
      4. clear browser cache.

      then try again.

      Regards, Mark.
    • Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
    • Sleeper's Avatar
    • Sleeper
    • Rocketeer
    • Posts: 55
    • Thanks: 0

    Re: Ugh. My whole site is toast - accidentally turned off a Rok

    Posted 11 years 5 months ago
    • MrT wrote:
      1. extensions manager > database > FIX button - should fix the tags error
      2. reinstall roksprocket extensions
      3. clear server cache - system > clear cache - tick all - DELETE
      4. clear browser cache.

      then try again.

      1. Nope. It did nothing. It is detecting nothing to fix
      2,3,4 Yes, thank you

      But the main problem still remains: Error loading component: com_tags, Component not found
    • Sleeper's Avatar
    • Sleeper
    • Rocketeer
    • Posts: 55
    • Thanks: 0

    Re: Ugh. My whole site is toast - accidentally turned off a Rok

    Posted 11 years 5 months ago
    • Also - I looked right at the db 'extensions' table. "com_tags" is simply not in there.

      Where do I get tho mysterious extension? I looked via FTP in 'components', and the files are there!

      So what to do? Manually add the db entries, because the files exist? Delete the files and see if the admin recognizes the need to install? (I will back up the folder, naturally)

      If anyone could post the row from the extensions table, containing the com_tags…

      PHEW! - I added the data to the extensions table, and the error went away.

      29 com_tags component com_tags 1 1 1 1 {"legacy":false,"name":"com_tags","type":"component","creationDate":"March 2013","author":"Joomla! Project","copyright":"(C) 2005 - 2013 Open Source Matters. All rights reserved.","authorEmail":"admin@joomla.org","authorUrl":"www.joomla.org","version":"3.0.0","description":"COM_TAGS_XML_DESCRIPTION","group":""} {} 0 0000-00-00 00:00:00 0 0
    • MrT's Avatar
    • MrT
    • Preeminent Rocketeer
    • Posts: 101084
    • Thanks: 13484
    • Web Designer/Developer

    Re: Ugh. My whole site is toast - accidentally turned off a Rok

    Posted 11 years 5 months ago
    • Go to extensions manager > discover - press discover button - tick on com_tags and click install.

      Regards, Mark.
    • Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
  • Re: Ugh. My whole site is toast - accidentally turned off a Rok

    Posted 11 years 3 months ago
    • Sleeper - my Joomla would not "discover" com_tags either - THANK YOU FOR THIS! It was the only answer that fixed my com_tags problem.
      Sleeper wrote:
      Also - I looked right at the db 'extensions' table. "com_tags" is simply not in there.

      Where do I get tho mysterious extension? I looked via FTP in 'components', and the files are there!

      So what to do? Manually add the db entries, because the files exist? Delete the files and see if the admin recognizes the need to install? (I will back up the folder, naturally)

      If anyone could post the row from the extensions table, containing the com_tags…

      PHEW! - I added the data to the extensions table, and the error went away.

      29 com_tags component com_tags 1 1 1 1 {"legacy":false,"name":"com_tags","type":"component","creationDate":"March 2013","author":"Joomla! Project","copyright":"(C) 2005 - 2013 Open Source Matters. All rights reserved.","authorEmail":"admin@joomla.org","authorUrl":"www.joomla.org","version":"3.0.0","description":"COM_TAGS_XML_DESCRIPTION","group":""} {} 0 0000-00-00 00:00:00 0 0

Time to create page: 0.068 seconds