VirtueMart Forum

VirtueMart 2 + 3 + 4 => General Questions => Topic started by: giriga on June 26, 2018, 16:39:19 PM

Title: update joomla 3.8.9
Post by: giriga on June 26, 2018, 16:39:19 PM
Hello, help! , I updated my Joomla 3.8.8 site with Virtuemart 3.2.14 at Joomla 3.8.9, my site is not working anymore I have this error: Fatal error: Uncaught Error: Class 'JClassLoader' not found in C: \ xampp \ htdocs \ furnitureamentionline \ libraries \ cms.php: 40 Stack trace: # 0 C: \ xampp \ htdocs \ furnitureamentline \ administrator \ includes \ framework.php (18): require_once () # 1 C: \ xampp \ htdocs \ furnitureamentline \ administrator \ index.php (40): require_once ('C: \\ xampp \\ htdocs ...') # 2 {main} thrown in C: \ xampp \ htdocs \ furnitureamentline \ libraries \ cms.php online 40
Title: Re: update joomla 3.8.9
Post by: GJC Web Design on June 26, 2018, 17:41:55 PM
None of that stack mentions VM .. --- so Joomla problem
Title: Re: update joomla 3.8.9
Post by: jenkinhill on June 26, 2018, 18:09:36 PM
Joomla 3.8.9 had already been superceded by J3.8.10 because of Windows server issues.  https://www.joomla.org/announcements/release-news/5737-joomla-3-8-10-release.html
Title: Re: update joomla 3.8.9
Post by: giriga on June 26, 2018, 18:58:56 PM
I updated to 3.8.10 I solved the problem, but now I still have this problem during the purchase (see image)
Title: Re: update joomla 3.8.9
Post by: GJC Web Design on June 26, 2018, 19:33:42 PM
again - Joomla - not VM
Title: Re: update joomla 3.8.9
Post by: jjk on June 26, 2018, 22:19:46 PM
Perhaps switch the Joomla mailer to 'SMTP'?
Title: Re: update joomla 3.8.9
Post by: aftertaf on July 03, 2018, 23:57:37 PM
versions of xampp / PHP being used are . . . ?
Title: Re: update joomla 3.8.9
Post by: Studio 42 on July 04, 2018, 03:24:00 AM
Quote from: giriga on June 26, 2018, 18:58:56 PM
I updated to 3.8.10 I solved the problem, but now I still have this problem during the purchase (see image)
Report this problem to your server support, else  you can use sendmail or smtp to solve it. This is not a Vm bug.