I come here with a problem that I can not solve.
I have a prestashop in version 1.7 that I have moved to another server, it is worth mentioning that in the old server the prestashop is working well.
When I have migrated the prestashop to the new server, everything works well except when I want to enter the Backoffice, when I want to enter the Backoffice, simply leaves the page blank.
I have activated the debug mode, but it doesn't give me any error related to Backoffice, the interesting thing is that when the debug mode is activated, I can enter the Backoffice without problem.
The only thing I can see is that it gives me an error 500 but it doesn't tell me anything else.
I don't know if anyone can give me any idea of what might be happening in this case, thank you.
When you have this kind of problem, the best solution is to remove the cache:
On Prestashop 1.6: delete the contents of the cache / smarty / cache and cache / smarty / compile folders
On Prestashop 1.7: delete the var / cache folder
Regards,
Remove all cache. Delete files in /app/cache
I think can not be solved by deleting cache you should debug it further.
Most probably the error could be due to php version change.
follow this steps:
Check php version of old hosting
apply php version of old hosting to new one
Related
I'm Looking for a kind of guide how to migrate extensions to work with TYPO3 V10.
I don't find much when I try my luck on google and don't really know where to start.
We are actually using TYPO3 9.5 and I will need to migrate Comsolit's owl_slider which we are heavily using on our website. TER doesn't offer a Version for TYPO3 V10.
Any hints are appreciated.
Since it is not built by you, if an update comes, all of your changes will be overwritten. With that being said, if you decide that you want to update it to TYPO3 10 by yourself then you should first avoid the "*" if you are on composer mode and you have to insert the current version so next time you run composer update, composer won't update the extension. Still, composer will check if the extension is compatible with TYPO3 v10 and if not then it will not run. So you will have to remove it from the composer and manually download it to your ext directory. If you are on non composer mode, just avoid clicking the update button in the extension manager.
For Frontend not much have been changed. The most common error that you can get is the <f:switch/> viewhleper where the defualt case has been changed from default="true" to defaultCase Changes.
Now you will have to deactivate the extension and update your TYPO3 installation to v10.
The first thing you need to do is to change the TYPO3 dependency to 10.99.99 or something greater than your current version (ext_emconf.php). From this point on, is try and error. You have to install the extension and go step by step through the errors that appear if any. Here you can find the changes that have been made. It would be wise to avoid deprecated function since in TYPO3 11 or 12, will be removed.
https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog-10.html
You can not know rom the start what can go wrong unless you test it. Even if you know exactly what has been changed, you will still need to try and error.
Best regards
I am using DNN 9. I recently upgraded DNN from version 9.1.1 to 9.3.2. When I Login, the left side of DNN disappears with only the logo od DNN. Other options like settings,edit etc are not seen. Any Idea as to what the issue might be?
If you search the forums at dnnsoftware.org, you'll probably find the solution. I'm afraid that I don't recall what it is.
I think, though, that upgrading to 9.4.4 will fix it, too. You'll want to do that in a test environment to make sure that your upgrade will work. There may be some third party modules that need to be upgraded before you upgrade to 9.4.4, so check with module vendors.
As an addition to Joe's answer: There were Problems with the Newtonsoft JSON versions. Maybe this thread is helpful: https://www.dnnsoftware.com/forums/threadid/543186/scope/posts/persona-bar-not-displaying-completely
"...so check with module vendors": There are known issues with DNNSharp modules. See https://dnncommunity.org/forums/aft/748 - but better check with all vendors of third party extensions, if you use any.
Read a few things, tried this and it worked. Delete all from the Bin directory, grab and copy all from another bin directory from a currently working site with the exact version. You may need to install a demo/test site and spin it up to get a good working copy, but this worked for me.
Restoring the bin folder was the solution for me
Recently i moved from netbeans 6.9 to Netbeans 7.2, while working on 6.9, i have handy functionality of after deployed my project if i do modifications in html or jsp pages i can see when i refresh the page in browser. But while using 7.2 it's not available, so each time i need to build, and deploy for changes get updated.
So i gotta few suggestions like
1)
Check->Compile on save in project properties
Uncheck->Deploy on save in project properties, but still it's not working.
Any idea what i have missed.
Thanks in advance.!
I must say this scenario works fine for me - I don't see any problem. What kind of project are you using - Ant-based or Maven-based? The best thing would be if you can file a P2 issue in the netbeans.org bug database, so we can investigate. Thank you.
This happened to me as well. I tried renaming the project to a new name not the project folder and re run. It worked for me. Try for yourself.
Nitin.
I am trying to run Joomla on my local machine. I have installed wamp 2.0 and everything installed ok with it and I managed to see it running. I have now come to install Joomla 1.5.18 but I am having a problem with the mootools file on the installation wizard.
When running through the installation process in FireFox with firebug turned on I get errors about the mootools file missing a }. When I view the file through windows explorer it is complete and everything is fine with it but when I click on the error in firebug to see the error the file is truncated which I assume is why it is not working and complaining about a missing }. To test the file I created a test page which pulls in the same mootools file and this works fine (running locally and not through Joomla ).
Does anyone know why this is happening and how to fix it? I think it must be a problem with wamp as like I said the file is fine and runs ok if I run it from the file system, however I know nothing about servers so this is a guess. Maybe a limit on the size of a file which can be returned as the mootools file is around 7000 characters long.
I have tried un-installing both Joomla and Wamp but none this has not worked and I still get the same error. Thanks
I'm just curious, have you tried installing a newer version of Joomla? 1.5.8 is a little bit old and you may have better luck using something a version or two newer. Alternately speaking, if you're not a big fan of installing WAMP and then manually installing Joomla, you can use a Bitnami Joomla stack. Basically, Bitnami installs Apache, mySQL, PHP, and Joomla all in one quick and easy install.
I hope that some of this helps!
I would suggest that your problem is not with the Mootools package but with your template or modules that are loaded in. Can you turn off all of your modules and reenable them one by one until you see the error again?
I have a DotNetNuke Module created in DNN 4.9.2. It runs fine on my dev machine but when I post it to the live server, I just get a blank screen, well my skin with no content.
I have installed and then uninstalled, then reinstalled the module, same issue.
I must be overlooking something. Can anyone outline some ideas on how to trouble shoot this issue. I have done the following:
Check code - exact match
Check DNN Event Log - clean
Look for errors - none
Restart Site - same issue
Check Windows Logs - clean
Bang Head against desk - same issue, although now I have a headache
Any other ideas would be great
Make sure that the "Mode" selection at the top of the control panel isn't on Layout.
Are you running as an administrator? Otherwise, do you know that the user has rights to see the module?
The answer was a bug in my code. The reason I didn't see an error was because that an xslt file path was wrong and it didn't kick in my try catch. I corrected the path and violà.