Jump to content

tinman47

Members
  • Posts

    14
  • Joined

  • Last visited

Profile Information

  • Location
    Florida
  • Activity
    User/Merchant

tinman47's Achievements

Newbie

Newbie (1/14)

2

Reputation

2

Community Answers

  1. Before modifying your .htaccess file, the slow performance of your shop can be due to a number of reasons that aren't related to your .htaccess. First, check your caching. Go under "Advanced Parameters" and "Performance". Clear your cache, then enable your Smarty Cache, and enable memcache below. Reload your store and click around and your site should be considerably faster. Then check if you can enable CCC caches. Enable one at a time to make sure your site is loading properly, as some themes may be rendered incompatible. Your site should be considerably faster once that is completed. If you are still experiencing slow performance, it could maybe be a module that is slowing your site down. Go in the config file, store_root/config/defines.inc.php and set line 42 or debug profiling to true: define('_PS_DEBUG_PROFILING_', true); Reload your site and scroll to the bottom of your site and you should see exactly what is loading, and the latency of each module and SQL query in milliseconds. It might be a resource hungry module slowing down your site. The last thing I could think of is your hosting. Shared hosting packages tend to be slower since they share resources with other users. If you still don't see any speed increases, maybe other forum users have better suggestions. But these are all the methods that I use on stores I work on.
  2. I actually had this issue awhile back with version 1.6. I'm trying to save product quantities with Prestashop 1.7.0.5 and I get a successfully saved message, but nothing is saving. I go in the console and I'm seeing the error Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/. I though this error was already fixed with 1.6? What I can do to rectify this issue? Thanks
  3. Figured it out. Its a little more involved than I thought. Here's the solution in case anyone is trying to figure it out: Create AboutPageController.php and place inside root/controllers/front/ (You can place into a folder in this directory if you like).Here is the code for AboutPageController.php: <?php /* The classname here will be the name of the controller */ class AboutPageController extends FrontController { public function init(){ parent::init(); } public function initContent(){ parent::initContent(); $this->setTemplate('about'); } } Now go into your theme, and add the .tpl file into root/themes/current_theme/templates - In this case I'm adding about.tpl: {extends file='page.tpl'} {block name='page_header_container'}{/block} {block name='page_content'} {* Page content *} {/block} All HTML and page content goes into the block named "page_content". Now with that completed, go into your backend for Prestashop, go into "Traffic & SEO" and add a new page, then find your page and set whatever the rewrite is. And the final step (there are so many steps), is to go into app/cache/dev (or prod depending on what your environment is set to) - and delete the file class_index.php - That should be it.
  4. @Xpert-Idea: $this->setTemplate('about'); Ah so that partially worked. Put the .tpl template into the theme root and "templates" folder and now it works, but it is not loading any styles.
  5. Front-end controller overrides that worked for 1.6 don't translate over to 1.7 - Here is my about page controller code located in root/controllers/front It keeps returning a "No Template found error", but its in the directory AboutPageController.php: <?php /* The classname here will be the name of the controller */ class AboutPageController extends FrontController { public function init(){ parent::init(); } public function initContent(){ parent::initContent(); $this->setTemplate(dirname(__FILE__).'/templates/about.tpl'); } /* The following code portion is optional. * Remove the double-slashes to activate the portion * if you want to use external stylesheet and JavaScript for the page. * Create the CSS and JS files in the css and js directories of the theme accordingly */ public function setMedia(){ //parent::setMedia(); //$this->addCSS(_THEME_CSS_DIR_.'custom-page.css'); //$this->addJS(_THEME_JS_DIR_.'custom-page.js'); parent::setMedia(); $this->addCSS('custom_pages/custom-styles.css'); $this->addJS('custom_pages/custom-script.js'); } }
  6. I am managing a client's store, and while installing a new Authorize module, I set the store to Production (Test Mode), and forgot about it. They received a bunch of orders, and shipped out $3K worth of orders, but in Authorize they actually didn't receive anything.. Is there any way to receive payment through Authorize? Is there anyway to resend the order through prestashop? Am I screwed? Please help
  7. I am managing a client's store, and while installing a new Authorize module, I set the store to Production (Test Mode), and forgot about it. They received a bunch of orders, and shipped out $3K worth of orders, but in Authorize they actually didn't receive anything.. Is there any way to receive payment through Authorize? Is there anyway to resend the order through prestashop? Am I screwed? Please help
  8. This is late but looking for the answer for this exact issue and fixed it. Don't edit anything. Go in the back office and under "Performance", clear the cache. Then, clear your browser cache. Not sure why this works.
  9. This is super late but I was looking for a solution, found your post, and figured it out. For me at least, it was a caching issue. Go to "Advanced Parameters > Performance" and go the "CCC (COMBINE, COMPRESS AND CACHE)" options and disable "Apache Optimization". Once thats done, go to the top of the Performance configurations and clear the cache.
  10. So I'm trying to give a proper URL structure to my shop. Something to the effect of shopurl.com/staff/will So I create a CMS category "staff", then create a page under the category "will". Unfortunately Prestashop won't structure it and I get something to the effect of shopurl.com/content/3-will - it seems to bunch all pages into "content" and just slaps an ID number on it. I tried using 301 redirects as well. In the htaccess, I added various redirects like so: # Tried this one first RewriteRule ^staff/will$ http://shopurl.com/content/3-will [L,R=301] # Tried another RewriteRule ^staff/will$ http://shopurl.com/content/3-will [L,R=301] # Tried this one as well RedirectMatch permanent ^staff/will$ /content/6-will What am I doing wrong? Also I ideally don't want to disable friendly URLs.
  11. Okay so I went under "Performance" and disabled caching and that seems to work. Odd.
  12. I was made aware that information throughout the cart wasn't able to save because I had an early version of Prestashop that utilized XMLHTTPRequests. I've since updated my Prestashop version to 1.6.1.9 and I still can't save general product information. For example, I would enable a product and click "Save and Stay" and the page would refresh and get a successful message, but the product is still disabled. Whats strange is that if I click on "Save" instead, sometimes the information of the product would save and I can see the "Enabled" status when I'm searching for the product in the backend, but when I click on the product to edit, the information is reverted and the changes are lost. Even in the logs, it shows I'm editing and saving product information, but for some reason it's not being saved. Any ideas? Thanks
  13. So I had a problem where I couldn't save products or edit them. That resolved with the update, but when editing product combinations, sometimes they won't save, and I still get the Javascript error: jquery-1.11.0.min.js:4 Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/. Any ideas? Thanks
  14. I'm running PS version 1.6.1.7 and UPC codes and EAN-13 codes aren't saving when I save the product. Any solutions?
×
×
  • Create New...