while trying to upgrade magento using magento connect, after upgrading frontend and backend shows this error.
Fatal error: Class 'Mage_Sales_Model_Resource_Setup' not found in
/var/www/vhosts/dressfromeurope.com/avmmaxx/includes/src/Mage_Core_Model_Resource_Setup.php
on line 23 anyone can help?
It seems the compiler is turned on, turn it off (cache also) and retry.
If successful, run the compilation process again and enable compilation and cache.
Have u done some changes in core file(s) in magento.Because if some modification is done in core file(s) of magento, it causes problem while upgrading.
Related
I have updated joomla version from 3.6.5 to 3.7 joomla latest version.
Now I am getting fatal error on site backend :
Fatal error: Call to undefined method JAdminCssMenu::load() in /public_html/administrator/modules/mod_menu/mod_menu.php on line 25
Can anyone please provide me solution to get it fixed.
Thanks
The temp fix does work, (uncomment line 25). However I found it was a component that was causing the error, SP Page Builder, once uninstalled, all worked fine :D
I had the same issue but you don't need to uninstall SPPageBuilder, just go to yoursite.co.uk/administrator/index.php?option=com_modules&view=modules, filter by Administrator modules and unpublish the one called "SP Page Builder Admin Menu".
I have also received the same error on a couple sites so far after updating. I added a php override to my htaccess file to bring the sites back online. I added the following to the rewrite section of my htaccess file:
php_value memory_limit 128M
This increases the memory to 128MB. Not the best way to fix the issue, but it works right now. I don't know if this issue is related to the 3.7 upgrade or not, but it's awfully coincidental that 2 of my sites, and now coming across this post happened after upgrading. I wonder if there is a bug in the new Joomla version, or if it requires more memory now.
This is faced by many who used JSN Poweradmin. You need to uninstall it to run your Joomla site or you can simply comment out or delete this line on line no 25
//$menu->load($params, $enabled);
in the file /administrator/modules/mod_menu/mod_menu.php.
I have replaced mod_menu complete Directory/Files with old one (3.6.5) and its working now.
If you are using JSN Poweradmin and you tried to install SP Page Builder, Just go to this directory:
administrator\modules
and delete this folder: mod_sppagebuilder_admin_menu
Now Joomla Admin panel would work OK and also SP Page Builder component is ready to use.
I have tried to upgrade Joomla version from 3.5.1 to 3.6.4 from Joomla control panel by click on "Update Now" button. And got "ERROR: AJAX Loading Error: Forbidden"
Please see the screenshot http://easycaptures.com/fs/uploaded/1107/5217107686.jpg
How can i fix the issue? Thanks advance for helping !
Here is what I would do, make a site backup.
Then manually updated by extracting the update patch package in the root directory. Go to the link below and find the package that is specifically intended for updating from versions prior to 3.6.X
https://downloads.joomla.org/cms/joomla3/3-6-4
Joomla! 3.6.4 Upgrade Package (.zip)
This package is for performing updates from Joomla! 2.5 and previous 3.x releases to 3.6.4
Please let me know if you have any issues with updating in this manner.
Mike Hamanaka
mike#vertualize.com
707-267-1768
SOLVED THE PROBLEM !!!
Here is the total solution of my mentioned issue !! I tried hard to solve the issue in various way but failed.
I fixed my issue once followed this tutorials.
https://docs.joomla.org/J3.x:Upgrading_from_Joomla_3.4.x_to_3.5
Stay fine with Joomla !!!
"Forbidden" seems to indicate that there is a restriction accessing a file.
Some things to try:
temporarily revert to the default .htaccess file by backing up the current .htaccess file and copying htaccess.txt to .htaccess
reset file permissions by installing the free or paid version of Akeeba Admin Tools (if it's not already installed) and run the "Fix Permissions" tool
temporarily disable security extensions or tools that may be restricting access to the update files
In my particular case, it was the last suggestion which was relevant. I worked out how to bypass Sucuri as an administrator by adding an entry in my local hosts file to access
the website via its direct IP address. The update then worked flawlessly.
Today I did an upgrade to version 1.9.2.0 so that patch SUPEE-6285 also is installed, but halfway the installation (With Magento connect) the console showed an error screen similar to wat you see when the maintenance.flag file is in your root (503 error). The maintenance.flag was indeed in the root, but very strange that it showed up in the console.
After removing the maintenance.flag the site stayed blank, also the admin page. I can access the connect manager, but everything I want to install with the extension manager fails with this message "CONNECT ERROR: Package community/Interface_Adminhtml_Default failed: Unknown cipher in list: TLSv1"
How to fix this? If I look in the files, half of the files have the date of today and the other half an older date, so it looks to me that the installation broke down or something
In the file downloader/lib/Mage/HTTP/Client/Curl.php Change the code
$this->curlOption(CURLOPT_SSL_CIPHER_LIST, 'TLSv1');
to
if(isset($var)){$this->curlOption(CURLOPT_SSL_CIPHER_LIST, 'TLSv1');}
and problem will be solve for now.
Probably related to this issue, the Magento Connect subsystem attempts to fire up curl and use an SSL connection which has apparently not been disabled on all the Magento servers as you did have a partially successful upgrade.
As noted here and the previous link, the fix is to enable TLSv1 by editing downloader/lib/Mage/HTTP/Client/Curl.php to include the line:
$this->curlOption(CURLOPT_SSL_CIPHER_LIST, 'TLSv1');
We ran into the issue back in February when Magento de-Poodlized the servers.
Note: links are all Stack Exchange questions related to the issue in this section (StackOverflow) and Magento.StackExchange
I went to the file downloader/lib/Mage/HTTP/Client/Curl.php and find out there was a line with TLSv1 in it, so i put // in front of it and that solved the problem! Now i can do updates with connect!
But....
Now my site shows up with links that are not working and my admin stays blank...
Next problem...
If you have updated Magento to 1.9.2, you may encounter this error when using the downloader. The problem is due to older ciphers and remains an uncorrected bug. But this is fixed by adjusting one line of code.
To correct this, in downloader/lib/Mage/HTTP/Client/Curl.php, change:
$this->curlOption(CURLOPT_SSL_CIPHER_LIST, 'TLSv1');
to
$this->curlOption(CURLOPT_SSLVERSION, CURL_SSLVERSION_TLSv1);
I am trying to upgrade Magento 1.3.2.4 to 1.7 using Magento Connect Manager via 'magento-core/Mage_All_Latest' extension key to install. But I found the following error and I don't know how to reslove it.
Error -
Exception caught:
Warning: include(/N91nq64igkwi8oxu.php): failed to open stream: No such file or directory in /var/www/projects/spacecenter/lib/Varien/Autoload.php on line 93
If anyone faced this kind of error, please help.
Thanks in Advance!
I strongly recommend this upgrade guide from Turnkey - worked perfectly for me.
Please don't expect that everything works or looks the same once you've upgraded to Magento 1.7. Depending on what features or extensions you use, quite a bit of work might be needed until you're done. So don't do this on your live system. Better duplicate it to a development environment and test the upgrade there.
I'm trying to update the Joomla version on one of the website I managed.
I downloaded the package to upgrade to Joomla 1.5.25 (if my memory's good). I did a test on a dev website and everything worked well.
Now, when I apply the update to the current website, i receive the error : Fatal error: "Class JController" not found in */components/com_content/controller.php "
The line
jimport('joomla.application.component.controller');
is there.
Anyone has any idea?
Thanks a lot
try to upload the files again via FTP client. Sometimes files don't transfer properly or at all. Also make sure you downloaded the correct upgrade package related to your previous version.