I'm using nopCommerce 3.90 version. I downloaded yet and not change any code or settings.
I'm looking code base but when I looked admin views pages(Nop.Admin->Views->*), I saw an error
(no error nop.web views)
like below picture link
https://prnt.sc/vdw1ac
Please help me,
Best regards
Please check with asp.net core installation in your system, if it is not updated these error occurs check with the version required to run nocommerce and install it will work.
Related
I´m having problems understanding how to install a new theme in my magento 2.2 and i was hopping someone could help me understand what it is, what i did was:
I installed magento 2.2 from here. and then choose "Full release with sample data" community edition 2.2.0. The installation went well and i can access to my admin panel adn everything else.
Next i found this template and downloaded the package Bizkick v1.0.3, unzipped it and then i have two directories, which are "app" and "pub". After this i dragged these to my magento root, overwrite the ones that were there and now, i CANNOT access anything, not my initial page nor my admin, i have tried with other themes and the same thing keeps happening. I also have disabled my cache in the admin like the instructions said and them perform the above but with no luck.
Can anyone enligh me?
Regards.
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.
I just upgrade my Joomla website from 3.1.1 to 3.3.6.
As found on https://github.com/joomla/joomla-cms/releases/tag/3.3.6 I downloaded Joomla_3.3.6-Stable-Update_Package.zip pack and uploaded all the files over my previous Joomla installation.
Unfortunately, I cannot login and the following error is displayed:
Fatal error: Call to a member function checkSession() on a non-object in /home/www/.../web/plugins/user/joomla/joomla.php on line 209
Line 209: $this->app->checkSession();
I did additional tests and it seems that all the "$this-app->..." command fail!
I opened the 3.1.1 joomla.php file and found another syntax:
$app = JFactory::getApplication();
$app->checkSession();
Replacing the 3.3.6 syntax with this one solved my problem, but I can see that similar "calls" are done when logout, so I would need to change them as well.
It looks like the new syntax ($this->app->) is not working in joomla.php after upgrade to 3.3.6 and now I'm afraid similar errors can occurs in other scripts.
Does someone already get similar errors, is that a known problem with Joomla upgrade, how to solve this issue correctely?
Thank you in advance for your help.
Joel
Why on earth would you do this? For a long time now Joomla has had a built-in updater that does several things beyond just copying the files to the correct location, like updating the table definitions, adding new tables, data migration and removing old files.
My guess is that your database schema is now out of sync with the PHP. You'll have to role back to your backup as there is no clear way to say if records have been damaged etc.
Once you've restored your backup, use one of the methods described in the Upgrading from an Existing Version FAQ on Joomla's Doc's site.
As this question is about Joomla management and implementation details, you may get a better answer if you, try asking on the Joomla Q&A StackExhange site in the future.
I am experimenting with Joomla 3.1.4. Whenever I add a new module the template does not show at all in the front-end. The site is blank. On disabling the new module it starts showing properly again. Even a basic hello world type of module does not seem to work and nor does a third party extension I have tried.
I can see them in the extension manager and in the module manager and they have installed successfully. Frustrated with all this I decided to install a new 3.1 template which too installed successfully. However this template does not show anything in the front-end either with my module enabled. It almost seems that there is some sort of security restriction which is disabling the template from rendering whenever any change is made to the basic installation.
Can someone please give pointers to resolving this odd behaviour?
Probably one or some of the core files required for the modules to work are missing.
Head to Global configuration and make sure your Error reporting is set to development. Reload the page and update your question with the error message.
Why not try the newer Joomla 3.1.5 (Download page)? I know that 3.1.4 had at least one problem which could possibly cause server errors in conjunction with extensions (the most likely reason for the blank page that you see).
In general, when encountering a blank page, the first thing to do should be to check the error log of your webserver!