I have moved my website built using PrestaShop to a new Hosting provider. And now I can access the admin backend and the site looks correct (all the products and pricing and images are loading).
However I am not able to edit the products in the backend, nor any of the carrier or other options. What could be causing this problem?
These are the steps I followed when moving my PrestaShop website:
Created new database
Imported backup database
Edited config file with new DB name, username and password
This is my website: http://wow-maternity-sa.co.za
I am also able to register new users on the site, and they get added to the DB. I think this shows that the site is "linking" to the newly created SQL Db
I tried that, but no luck. I have picked this up in the error log, not sure if it is useful:
[04-Sep-2016 10:23:11 Africa/Johannesburg] PHP Fatal error: Uncaught --> Smarty: Unable to load template file 'controllers/carrier_wizard/helpers/form/form_ranges.tpl' in '/home/wowmat/public_html/admin123/themes/default/template/controllers/carrier_wizard/helpers/form/form.tpl' <-- thrown in /home/wowmat/public_html/tools/smarty/sysplugins/smarty_internal_templatebase.php on line 129
I was able to fix the “carriers” issue by changing the extension of “.tp” to “.tpl” of this file:
form_ranges.tpl in public_html/admin123/themes/default/template/controllers/carrier_wizard/helpers/form/
Related
Using stencil 3.0.3, node 12.21 cornerstone theme was working and suddenly stopped with a weird server error:
Debug: internal, implementation, error
Error: The BigCommerce server responded with a 500 error
at Object.internals.getResponse (/usr/local/lib/node_modules/#bigcommerce/stencil-cli/server/plugins/renderer/renderer.module.js:128:15)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async internals.implementation (/usr/local/lib/node_modules/#bigcommerce/stencil-cli/server/plugins/renderer/renderer.module.js:39:20)
at async module.exports.internals.Manager.execute (/usr/local/lib/node_modules/#bigcommerce/stencil-cli/node_modules/#hapi/hapi/lib/toolkit.js:45:28)
at async Object.internals.handler (/usr/local/lib/node_modules/#bigcommerce/stencil-cli/node_modules/#hapi/hapi/lib/handler.js:46:20)
at async exports.execute (/usr/local/lib/node_modules/#bigcommerce/stencil-cli/node_modules/#hapi/hapi/lib/handler.js:31:20)
at async Request._lifecycle (/usr/local/lib/node_modules/#bigcommerce/stencil-cli/node_modules/#hapi/hapi/lib/request.js:312:32)
at async Request._execute (/usr/local/lib/node_modules/#bigcommerce/stencil-cli/node_modules/#hapi/hapi/lib/request.js:221:9)
I have tried to re-install big commerce stencil, clean build and still get the same error.... at this point I have no idea what could be causing this issue.
Importantly, there was no code changes in between the day where everything was working and the day where it stopped.
Are you using CloudFlare for a CDN? I've ran into this issue and have had to edit my hosts file
I add the following 3 lines.
The first one is for the Store Domain, i.e. if you have MyShoeStore.com
The second 2 contain the auto-generated store-hash for a BigCommerce store that should be visible in your URL bar if you are on the BigCommerce control panel (Logged into the admin view - that's the easiest way to get it, there are some others)
35.186.223.98 mystoredomain.com
35.186.223.98 store-abcdefg[store-hash].mybigcommerce.com
35.186.223.98 www.store-abcdefg[store-hash].mybigcommerce.com
For some reason, Stencil-CLI gets thrown for a loop when trying to connect to a BigCommerce store that is running behind CloudFlare CDN. This has caused 500 errors in the Stencil-CLI, and a failure to render, during local development, but the store is able to be uploaded and hosted in production without a problem.
I'm not sure if this is the actual issue that you had which caused your 500 error, (It can be due to an error in the syntax of one of the HandleBars templates, but usually Stencil-CLI will output an informative error for that reason.)
The other situation I have seen this in is if you are trying to run Cornerstone on a very old BigCommerce store which is still running their old template framework (Blueprint) - in that situation, certain pages will 500, but others will work.
This may be helpful for others who are running into this.
I installed a proxy tool to capture traffic between stencil and BigCommerce in order to perhaps find more details on this error.
Unfortunately, as soon as I did that, the site worked again...
The Error
*polyfills.js:3050 GET https://localhost:9002/rest/v2/powertools/cms/pages?fields=DEFAULT&pageType=ContentPage&pageLabelOrId=/checkout&lang=en&curr=USD 404*
I am not able to perform checkout on both of my local powertools and electronics sites. The Chrome console log complains about the error shown above. Also, I have tried opening the given link in a new tab and it says No content page found matching the provided label or id: /checkout. Checked the WCMS Pages in my local Backoffice, I couldn't find any page with label or id as "checkout".
Could it be that I have to setup my local with the b2c_for_spartacus? (I have setup mine with b2c_b2b_acc_oms recipe instead)
Have you installed your SAP Commerce instance with the Spartacus Sample Data AddOn? The standard Powertools data setup will not include this, but the additions in spartacussampleadataaddon do. Please see links/instructions in https://sap.github.io/cloud-commerce-spartacus-storefront-docs/installing-sap-commerce-cloud/
If installed/setup correctly you should have a content page with UID=Checkout in the powertools-spaContentCatalog content catalog
I am having an issue only in Prod AEM 6.3 author instance. We have our application extending wcm core v1.
When user is logged in a content-author; and opens page properties; Only Basic, Advanced, Thumbnail tabs are accessible.
Selecting other tabs like; Cloud Services; Personalization; Permissions; Live Copy, donot open the tab. Rather stays with already opened tab only.
This is happening only in my production author instance. When I delete my local repository; start a fresh vanilla instance and deploy my code, this issue is not happening.
At certain point, our production author broke. Couldnt conclude it is code, since same code works fine in vanilla instance.
Has anyone faced similar issue? Is there any lead to troubleshoot this issue? All tabs works when logged in as admin. Fails only as author.
Looks like this issue is faced by few others. So posting my finding as answer as well.
This was indeed permission issue. OTB Author group did not have permission to /etc/cloudservices. So opening page properties was throwing error:
11.09.2018 10:24:48.597 ERROR [199.243.161.18 [1536675888296] GET /mnt/overlay/wcm/core/content/sites/properties.html HTTP/1.1]
org.apache.sling.engine.impl.SlingRequestProcessorImpl service:
Uncaught SlingException java.lang.NullPointerException: null at
org.apache.jsp.libs.cq.cloudserviceconfigs.components.configurations.configurations_jsp
I was stuck since I didnt know exact path. Trail n error, figured the missing path and granted permission to resolve.
Bonus Interesting Permission issue: Author group donot have permission to /config/ nodes.
So the RTE plugins were not loading for us coz path was like this:
After lot of digging, found this issue. Fix was to rename /config/ to /configuration/ and add property configPath=configuration to the parent node.
i have the following simple script to list the ftp accounts
but i am unable to get it to work as i have the following error as soon as it tries to call the constructor
include '/usr/local/cpanel/php/cpanel.php';
$cpanel = new CPANEL(); // Connect to cPanel - only do this once.
// List FTP account information.
$list_ftp_accts = $cpanel->uapi('Ftp', 'list_ftp');
echo "<pre>";
print_r($list_ftp_accts);
Fatal error: Uncaught exception 'RuntimeException' with message 'There
was a problem fetching the env variable containing the path to the
socket' in /usr/local/cpanel/php/cpanel.php:146 Stack trace: #0
/public_html/uapi.php(4): CPANEL->__construct() #1
{main} thrown in /usr/local/cpanel/php/cpanel.php on line 146
Line 146 in cpanel.php
$socketfile = getenv('CPANEL_PHPCONNECT_SOCKET');
According to a post on the cPanel forums, you can only use LiveAPI from within cPanel's document root, meaning your code would need to be in either /usr/local/cpanel/base/frontend/ or /usr/local/cpanel/base/3rdparty/. I ran into this while trying to use it in a WHM plugin (which would reside in /usr/local/cpanel/whostmgr/docroot/), and apparently that causes the same problem. If you're trying to run this from within cPanel or WHM, this page has some debugging steps you can try walking through.
If you're trying to run this code on a different server or from within a normal website's hosting account, you'll definitely need to use a different interface, such as the XML or JSON API. These are unfortunately somewhat confusingly documented, but the Guide to WHM API 1 page should get you started.
Me too got the same error.
Try changing your file extension to your_file.live.php, instead of your_file.php. It solved the issue for me.
Referred the documentation here.
I m Doing Iphone/Android push notification in joomla using Zend library it is working properly in Core php but it shows error in joomla when submitting a form LIKE :
**
An error has occurred while processing your request. You may not be
able to visit this page because of: an out-of-date bookmark/favourite
a mistyped address a search engine that has an out-of-date listing for
this site you have no access to this page Home Page If difficulties
persist, please contact the System Administrator of this site and
report the error below.
0 "Zend_Uri_Http" not found Powered by Joomla!®
**
If there is any way to resolve this error plz. let me khow the help will be appriciated...
Thanks in advance.
Amit Raval
NOT FOUND error occurs when your include file is not loaded. try to include ZEND LIBRARY FILE which loads "ZEND_URI_HTTP" file...
require_once 'Zend/Loader.php';
Zend_Loader::loadClass('Zend_Uri_Http');
You need to set path as per your current location of directory
suppose if you are in component/controllers direcotory
use like:
require_once JPATH_COMPONENT.'controllers/Zend/Loader.php';
Zend_Loader::loadClass('Zend_Uri_Http');
It must be done throughout all zend files to solve this issue.
Regards