News:

You may pay someone to create your store, or you visit our seminar and become a professional yourself with the silver certification

Main Menu

Error after upgrade - help needed

Started by Greatdanes, April 26, 2015, 09:30:41 AM

Previous topic - Next topic

Greatdanes

Using
Joomla 3.4.1
VM 3.0.6.2

After some days with templates mistakes I did take the big step and upgraded my site from 2.5.x to latest Joomla version and all did go well until I looked at my site.

Now I get the following message:
1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '), 0 , IF(f.category_parent_id = 0, -1, f.category_parent_id)) AS parent FROM j' at line 2 SQL=SELECT DISTINCT a.virtuemart_category_id AS id, IF(a.virtuemart_category_id in (), 0 , IF(f.category_parent_id = 0, -1, f.category_parent_id)) AS parent FROM jos_virtuemart_categories_da_dk AS a LEFT JOIN jos_virtuemart_category_categories AS f ON a.virtuemart_category_id = f.category_child_id LEFT JOIN jos_virtuemart_categories AS b ON a.virtuemart_category_id = b.virtuemart_category_id WHERE b.published='1' AND a.virtuemart_category_id = f.category_child_id

What can I do easy and fast to get the site online again?

GJC Web Design

I don't recognise that query

r u sure it isn't from a 3rd party extension ?  Try unpublishing everything except core VM stuff
GJC Web Design
VirtueMart and Joomla Developers - php developers https://www.gjcwebdesign.com
VM4 AusPost Shipping Plugin - e-go Shipping Plugin - VM4 Postcode Shipping Plugin - Radius Shipping Plugin - VM4 NZ Post Shipping Plugin - AusPost Estimator
Samport Payment Plugin - EcomMerchant Payment Plugin - ccBill payment Plugin
VM2 Product Lock Extension - VM2 Preconfig Adresses Extension - TaxCloud USA Taxes Plugin - Virtuemart  Product Review Component
https://extensions.joomla.org/profile/profile/details/67210
Contact for any VirtueMart or Joomla development & customisation

Greatdanes

You're a genius - the problem is solved thanks for the tip about looking elsewhere for error than the most obvious  :)