Prestashop: Theme - prestashop

I have upgraded Prestashop from 15.6.X.X to 16.X.X.X. After the up-gradation, default-bootstrap is activated as a default theme.
When I try to active my theme, the front end page get blank page.
It showing an error, Fatal error: Uncaught exception 'SmartyException' with message 'Unable to load template file .
How can I activate the old theme in upgraded version?
Please advice.

It seems that you miss a .tpl on your theme, please try to re upload it. (Or maybe your theme isn't compatible with 1.6)

There are often problems with Prestashop upgrades.
You need to completely fix all problems before using your template.
Try to option file config/defines.inc.php and change the site to dev mode
/* Debug only */
if (!defined('_PS_MODE_DEV_'))
define('_PS_MODE_DEV_', true);
All errors will show on your frontpage, try to fix all those errors and get your website totally works. Normal you will see problems with database, some tables was not successfully added new columns, then try to add those columns manually via your phpmyadmin
Good luck!

#2plus
Prestashop 1.5+ theme will not work in 1.6 there are lots of changes need. You can enable the debut mode and then you will find the error.
in 1.6 there is new tpl implement global.tpl may be that is missing.

Related

Configure an existing theme on Shopify

I'm totally new with Shopify, im trying to Configure an existing theme and fallow the full process form the guideline here (https://shopify.github.io/themekit/) but when I try to run the command theme download it shows me the error
requested theme was not found
though I setup Private apps and configure everything
so is there anything that I missed out of the box.
First of all try to grab Correct ID of your Store from here: https://www.screencast.com/t/ZySPCKUTi
https://www.screencast.com/t/If0MHah3
And run CMD Command from your destination folder path.
This error is showing when you use the wrong theme ID, check it.

Prestashop Productcomments Module Issue

I am experiencing a problem with the Productcomments module which I am using in a custom module and I cannot figure out how to fix it. The problem is with the star rating in the Productcomments form itself. This form works perfectly in a localhost environment - see images 1 and 2, but not on a live server - see images 3 and 4. On the live server it is showing no stars, just radio buttons, and no delete button for removing the stars.
Form as it looks on WAMP
Code from Chromes Inspect for WAMP
Form as it looks on Live Server
Code from Chromes Inspect for Live Server
Disabling the link to the following 2 js files recreates the problem on the local server which would suggest that the problem lies in the links to these two files on the live server, however I have checked all links to these files and they are correct, as are the permissions for these files.
jquery.rating.pack.js and productcomments.js
Occasionally when I clear cache under Advanced Parameters > Performance I get the following error message:
Fatal error: Uncaught --> Smarty: unable to write file /home/productm/public_html/cache/smarty/compile/10/e2/20/wrt5cbbb0747109d3_91450142
<-- thrown in /home/productm/public_html/tools/smarty/sysplugins/smarty_internal_write_file.php on line 46
This problem applies to all 1.6 versions of Prestashop tested.
Any suggestions on how to fix this problem would be appreciated.
Thanks
Kathleen
The error code you've got from clearing cache is linked to permission problems.
Here's probably a duplicate of your issue: How to fix erorr "Fatal error: Uncaught --> Smarty: unable to write file"?
Check that your prestashop files are set to 644 and folders 755 permission. (not just the js files you've mentioned).
Also if you manually moved the module to your live server(ftp), check the ownership of those files.
Edit:
I'll add this to the answer since the permissions didn't fix your problem.
looks like you have a prestashop bug going on with the JS (Synchronous loaded scripts)
here's a patch to fix that, maybe it fixes your original problem.
https://github.com/PrestaShop/PrestaShop/pull/6749/commits/73fd8dbed9f413a70f7d04fc4badd48f00ca501a

BigCommerce Stencil - TypeError: window.stencilBootstrap is not a function

Since around 10:30am EST today, I have been unable to apply stencil custom themes successfully. Any theme bundled before 10:30am EST today works fine when applied to a storefront. The themes work fine locally, and there are no errors when bundling, but once the theme is applied, the page loads HTML without images or any styling applied. The error in the console reads "TypeError: window.stencilBootstrap is not a function".
I have verified the issue on multiple accounts, and even occurs when trying to bundle and apply a fresh Cornerstone clone.
There are no reported issues on status.bigcommerce.com
Is anyone else having similar issues today?
Do I need to update my CLI?
Thanks
At the time of giving command stencil bundle, it will clear 'assets/dist' files. So that throws error theme-bundle.main.js file missing and window-stencilBootstrap is not a function.To avoid Clearing 'assets/dist' follow below steps.
Comment this below line in webpack.conf.js which is in root folder
/new CleanWebpackPlugin(['assets/dist'], {
verbose: false,
watch: false,
}),/
After this, run stencil bundle 'asset/dist' folder will not clear by doing so. Check u have 'assets/dist' folder then upload. After uploading your theme, front end will works fine.
This is a bug at stencil-cli.
There is an open issue for it: https://github.com/bigcommerce/stencil-cli/issues/379
I have just submitted a pull request with a possible fix: https://github.com/bigcommerce/stencil-cli/pull/409
In the issue, I suggest a workaround which can be done in the theme, without having to modify stencil-cli.
At stencil.conf.js, remove these two lines from the top of the file:
var webpack = require('webpack');
var webpackConfig = require('./webpack.conf.js');
Copy them as the initial lines of development and production functions, where these variables are actually used.
This change usually fixes the issue.

typo3 update 4.7 -> 6.2 - broken backend

I've performed an update from typo3 4.7.20 to 6.2.15. The process worked fine and there were no critical errors while running the install tool.
The frontend looks fine but the backend is broken:
I've removed all uncompatible extensions before I run the update. I've also checked all settings in the installationtool und deleted the temp/cache folder first.
I've got the feeling that the error is caused by the TemplaVoila! extension, I'm using v. 1.9.8. Firebug does not shows any error.
Does anyone had a similar problem and have already solved it?
Thank you very much!
I have come across this one multiple times. More often it is because there is a broken TBE_STYLES. I suggest you look around for $TBE_STYLES in your typo3conf folder and disable it for the time being. Most likely it will be in the extTables.php or some other file which is included dynamically.
seems BE is working, but you css does not got loaded.
check your 'web inspecter' to see if you get errors on loading CSS.
clear your cache (remove everything in typo3temp) and try again

PrestaShop Fatal error in module Api: syntax error, unexpected T_FUNCTION, expecting ')'

When I enter prestashop back office and click the modules tab in the top menu it is giving the following error, prestashop version 1.5.3.1
[PrestaShop] Fatal error in module Api:
syntax error, unexpected T_FUNCTION, expecting ')'
Any help would be greatly appreciated, searched prestashop forums and cannot find a solution
Thanks in advance
It may be related to version of PHP. I had this problem because of unsupported version of module. What I did was turn on the debug mode on PrestaShop which showed me in what module error was happening and then just removed that module from PrestaShop installation diretory, modules folder.
If you are using that module, you could backup it, then re-installing it, etc.
It turned out it was a problem with Youstice v1.7.2 module
It was causing the API error, what we did in the end was change the name of a folder in the public_html>modules from- "yousticeresolutionsystem" to "yousticeresolutionsystemX"
because it wouldn't allow me to delete the folder to stop the API error.
By using X this in effect deletes the folder stopping the error