Author Topic: VM 3.8.8 issue  (Read 928 times)

bratamic

  • Beginner
  • *
  • Posts: 12
  • A beginner
VM 3.8.8 issue
« on: June 05, 2021, 23:28:58 pm »
Good day. Does anybody know how to help me with a issue that I'm facing after updating to Virtuemart 3.8.8. I am unable to select "product categories" in the back end. The webpage just goes blank. What is strange is that after clicking the "product categories" link, The joomla favicon changes to my sites favicon and the page goes blank. I also updated the vmbeez3 template to 3.4.2 but I see no change to VM backend on any tabs. I think the issue may lie with this as it does not appear like displayed on the Virtuemart update page.

joomla 3.9.27
virtuemart 3.8.8
php 7.4

GJC Web Design

  • 3rd party VirtueMart Developer
  • Super Hero
  • *
  • Posts: 10185
  • Virtuemart, Joomla & php developer
    • GJC Web Design
  • VirtueMart Version: 3.6.8
Re: VM 3.8.8 issue
« Reply #1 on: June 06, 2021, 12:07:21 pm »
GJC Web Design
VirtueMart and Joomla Developers - php developers http://www.gjcwebdesign.com
VM3 AusPost Shipping Plugin - e-go Shipping Plugin - VM3 Postcode Shipping Plugin - Radius Shipping Plugin - VM3 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
http://extensions.joomla.org/profile/profile/details/67210
Contact for any VirtueMart or Joomla development & customisation

bratamic

  • Beginner
  • *
  • Posts: 12
  • A beginner
Re: VM 3.8.8 issue
« Reply #2 on: June 07, 2021, 09:59:02 am »
Thanks I tried following that thread but did not see any errors when enabling debug nor in the server logs. If I inspect element I see "display : none". Would this still be a characteristic of WSOD? I am on a pro version server at Inmotion so I don't think its a resource issue.

bratamic

  • Beginner
  • *
  • Posts: 12
  • A beginner
Re: VM 3.8.8 issue
« Reply #3 on: June 07, 2021, 10:24:20 am »
To tell you the truth the best solution for me was to restore my website back to VM 3.6.10 which is a shame because there seemed to be a lot of new features. On closer inspection the latest VM version caused many frontend modules to break too. Will carry on trying to get it working on me dev site.