spring00

This job is now closed. Many thanks to member Oexo France who sorted it out very quickly and professionally. I am happy to recommend him to others as I think he is brilliant

Thank you

We have customised the Blackhawk theme and it has created problems. We needed a transparent fixed header and full width slider which has affected the working of the site. - The quick view mouse over facility over the Featured products does not work (this is not a major worry) - The site looks terrible on smaller screens - The responsive menu does not work We need someone who really knows Prestashop 1.6 to sort out the responsive views of the site please. If they also know what is going wrong with the Quick View then even better. It failed when we increased the size of the container. Changing the global.js didnt work. The site is closed to the public but I can open it temporarily or give you private login details. As Christmas is here we really need it open asap

Hi the site isnt live yet so I can only share login privately. The only js I changed was the paypal.js which was affecting the voucher code facility (it wouldnt appear without an edit of the js).

Thanks for your response. I have worked out that the main error is caused by increasing the width of the container which has affected the quick view mouse over. I've created a new post on the forum as this post was created when the site seemed to have lots of errors. We turned off the ps debug mode and today it seems just this one problem remains.

Hi! I cant work out how to sort out this problem. I've changed the width of my website to 1450px but now the hover over the featured products to show Quick View wont work. I found this post http://www.prestashop.com/forums/topic/326126-solved-when-change-container-max-width-then-product-container-hover-doesnt-work/?do=findComment&comment=1852689 But the advice given doesnt work for wider sizes only smaller sizes. Can anyone please help?

Thanks El Patron. I may need paid help but for now I am working with a friend to try to sort it . I just wanted to share how we are tackling this problem in case it helps anyone else. Basically I kept back up copies of everything including work in progress. So we've been replacing edited files with original or earlier versions to work out where the error lies. This has worked well so far. By process of elimination it is clearly my fault and the problem has been mistakes with coding. I've used WinMerge which is great at comparing two versions of the same files to see what is different. I've also been using the W3C css validator tool to identify css errors. We are not there yet but I feel we are making progress.

Thanks for your response. I dont want the site to go live yet. I can provide login details privately if thats acceptable.

Hi! I just tried your site and it worked fine for me. I am using Firefox. Perhaps it works on certain browsers? Have you tried switching on the error messages? You could put the maintenance page up and switch on the errors and then come back and post what it says? To switch it on go to config/defines.inc.php and look for defines.inc.php. Look for the line near the beginning which is /* Debug only */ define('_PS_MODE_DEV_', false); Change the last word so it says /* Debug only */ define('_PS_MODE_DEV_', true); Save it and then try your cart again. Dont forget to turn it back to false when you are done. Good luck!

My website is ready to go live but suddenly the cart has stopped working. The ajax mouse over has stopped too and the product name disappeared on the front page. I should explain that the blockcart module is working fine in the header part of the site. But when I put the mouse over a product on the front page nothing happens. You cant see the 'More' or 'Add to cart' buttons anymore. It was quite a heart stopping moment as I just had decided that the site was ready to be publish Here is my error message Impossible to add the product to the cart. textStatus: 'parsererror' errorThrown: 'SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data' responseText: Notice: Use of undefined constant _RIJNDAEL_KEY_ - assumed '_RIJNDAEL_KEY_' in /var/sites/g/mydomain.co.uk/public_html/classes/Cookie.php on line 80 Notice: Use of undefined constant _RIJNDAEL_IV_ - assumed '_RIJNDAEL_IV_' in /var/sites/g/mydomain.co.uk/public_html/classes/Cookie.php on line 80 Warning: Cannot modify header information - headers already sent by (output started at /var/sites/g/mydomain.co.uk/public_html/classes/Cookie.php:80) in /var/sites/g/mydomain.co.uk/public_html/controllers/front/CartController.php on line 56 {"products":[{"id":9,"link":"http:\/\/www.mydomain.co.uk.gridhosted.co.uk\/classic-fitted-tee\/9-blue-fitness-t-shirt.html#\/size-s","quantity":1,"image":"http:\/\/www.mydomain.co.uk.gridhosted.co.uk\/35-home_default\/blue-fitness-t-shirt.jpg","image_cart":"http:\/\/www.mydomain.co.uk.gridhosted.co.uk\/35-cart_default\/blue-fitness-t-shirt.jpg","priceByLine":"\u00a3 19.99","name":"Fitted Tee (Blue)","price":"\u00a3 19.99","price_float":19.99,"idCombination":159,"idAddressDelivery":0,"is_gift":false,"hasAttributes":true,"attributes":"S","hasCustomizedDatas":false,"customizedDatas":[]},{"id":15,"link":"http:\/\/www.mydomain.co.uk.gridhosted.co.uk\/classic-fitted-tee\/15-black-fitness-t-shirt.html#\/size-s","quantity":1,"image":"http:\/\/www.mydomain.co.uk.gridhosted.co.uk\/47-home_default\/black-fitness-t-shirt.jpg","image_cart":"http:\/\/www.mydomain.co.uk.gridhosted.co.uk\/47-cart_default\/black-fitness-t-shirt.jpg","priceByLine":"\u00a3 19.99","name":"Classic Fitted Tee (Black)","price":"\u00a3 19.99","price_float":19.99,"idCombination":139,"idAddressDelivery":0,"is_gift":false,"hasAttributes":true,"attributes":"S","hasCustomizedDatas":false,"customizedDatas":[]}],"discounts":[],"shippingCost":"\u00a3 0.00","shippingCostFloat":0,"wrappingCost":"\u00a3 0.00","nbTotalProducts":2,"total":"\u00a3 39.98","productTotal":"\u00a3 39.98","freeShipping":"\u00a3 0.00","freeShippingFloat":0,"hasError":false,"crossSelling":""} The cart has been working great until today so I am wondering if I have done anything to upset it? Does anyone know what might cause a conflict? I had to edit the Paypal module today as it was stopping voucher codes appearing. But I dont think that is the cause as I've tried disabling the paypal module and that made no difference. Today I have been working on the css for the shopping cart today and I havent touched the products side of things. I've just realised that the cart process doesnt work at all with the error notification switched on (defines.inc.php). I've really messed this up and I dont know how Any help or suggestions would be gratefully received as the site needs to go live asap.

Hello. I've added a description to one of my category cms pages but the page is only displaying a list of the sub-category pages. How can I get the description to appear? I've checked the category.tpl of my theme (Blackhawk) and it seems ok but I am not very good at php. I've cut and pasted the category.tpl below in case there is an error in it. {if isset($category)} {if $category->id AND $category->active} {if $scenes || $category->description || $category->id_image} <div class="content_scene_cat"> {if $scenes} <div class="content_scene"> <!-- Scenes --> {include file="$tpl_dir./scenes.tpl" scenes=$scenes} {if $category->description} <div class="cat_desc rte"> {if Tools::strlen($category->description) > 350} <div id="category_description_short">{$description_short}</div> <div id="category_description_full" class="unvisible">{$category->description}</div> <a href="{$link->getCategoryLink($category->id_category, $category.link_rewrite)|escape:'html':'UTF-8'}" class="lnk_more">{l s='More'}</a> {else} <div>{$category->description}</div> {/if} </div> {/if} </div> {else} <!-- Category image --> <div class="content_scene_cat_bg" {if $category->id_image}style="background:url({$link->getCatImageLink($category->link_rewrite, $category->id_image, 'category_default')|escape:'html':'UTF-8'}) 0 top no-repeat; background-size:contain; min-height:{$categorySize.height}px;" {/if}> {if $category->description} <div class="cat_desc"> <span class="category-name"> {strip} {$category->name|escape:'html':'UTF-8'} {if isset($categoryNameComplement)} {$categoryNameComplement|escape:'html':'UTF-8'} {/if} {/strip} </span> {if Tools::strlen($category->description) > 350} <div id="category_description_short" class="rte">{$description_short}</div> <div id="category_description_full" class="unvisible rte">{$category->description}</div> <a href="{$link->getCategoryLink($category->id_category, $category->link_rewrite)|escape:'html':'UTF-8'}" class="lnk_more">{l s='More'}</a> {else} <div class="rte">{$category->description}</div> {/if} </div> {/if} </div> {/if} </div> {/if} <h1 class="page-heading{if (isset($subcategories) && !$products) || (isset($subcategories) && $products) || !isset($subcategories) && $products} product-listing{/if}"><span class="cat-name">{$category->name|escape:'html':'UTF-8'}{if isset($categoryNameComplement)} {$categoryNameComplement|escape:'html':'UTF-8'}{/if}</span>{include file="$tpl_dir./category-count.tpl"}</h1> {if isset($subcategories)} <!-- Subcategories --> <div id="subcategories"> <p class="subcategory-heading">{l s='Subcategories'}</p> <ul class="clearfix"> {foreach from=$subcategories item=subcategory} <li> <div class="subcategory-image"> <a href="{$link->getCategoryLink($subcategory.id_category, $subcategory.link_rewrite)|escape:'html':'UTF-8'}" title="{$subcategory.name|escape:'html':'UTF-8'}" class="img"> {if $subcategory.id_image} <img class="replace-2x" src="{$link->getCatImageLink($subcategory.link_rewrite, $subcategory.id_image, 'medium_default')|escape:'html':'UTF-8'}" alt="" width="{$mediumSize.width}" height="{$mediumSize.height}" /> {else} <img class="replace-2x" src="{$img_cat_dir}default-medium_default.jpg" alt="" width="{$mediumSize.width}" height="{$mediumSize.height}" /> {/if} </a> </div> <h5><a class="subcategory-name" href="{$link->getCategoryLink($subcategory.id_category, $subcategory.link_rewrite)|escape:'html':'UTF-8'}">{$subcategory.name|truncate:25:'...'|escape:'html':'UTF-8'|truncate:350}</a></h5> {if $subcategory.description} <div class="cat_desc">{$subcategory.description}</div> {/if} </li> {/foreach} </ul> </div> {/if} {if $products} <div class="content_sortPagiBar clearfix"> <div class="sortPagiBar clearfix"> {include file="./product-sort.tpl"} {include file="./nbr-product-page.tpl"} </div> <div class="top-pagination-content clearfix"> {include file="./product-compare.tpl"} {include file="$tpl_dir./pagination.tpl"} </div> </div> {include file="./product-list.tpl" products=$products} <div class="content_sortPagiBar"> <div class="bottom-pagination-content clearfix"> {include file="./product-compare.tpl" paginationId='bottom'} {include file="./pagination.tpl" paginationId='bottom'} </div> </div> {/if} {elseif $category->id} <p class="alert alert-warning">{l s='This category is currently unavailable.'}</p> {/if} {/if}

We are using Prestashop 1.5.4.1 with a customised version of the default theme. We have copied our Prestashop to a new host today by copying the ftp files over, exporting and importing the database via phpMyadmin and then changing the config details. It seems to have worked ok apart from one really frustrating problem. In the back office all the menu buttons at the top e.g. Catalog, Orders, Customers, etc no longer show as drop down menus. Instead all the drop down menu options are displayed. This styling issue is also affecting the Quick Access and Search boxes. It makes it impossible to use the Back office when we try to install modules for example. I have attached a screenshot to show what I mean. I've also attached a screenshot of how it should look (taken from the original copy). I can see that the layout of the Backoffice is determined by the admin.css. I've made sure this file is correct and no changes have been made to the copy. Please can anyone suggest anything for me to try? I have no idea what is causing this problem and I don't know if I should wipe the entire installation and start again from scratch. I really hope not. By the way the error logging is switched on but no errors are showing.

Hello. I have returned to prestashop after almost giving up with frustration at the bugs in earlier versions which cost me a lot of money. Now I have decided to try prestashop 1.6.0.6 for a new client with a lot of intrepidation. I've just installed it (automatic install via Vidahost web host) and switched on error logs. Straight away I cannot login. So I gave up, deleted the installation and done a fresh install. I still cant log in and I am getting the same cookie error message with both installations. Notice: Use of undefined constant _RIJNDAEL_KEY_ - assumed '_RIJNDAEL_KEY_' in/var/sites/g/mydomain.co.uk/public_html/classes/Cookie.phpon line 80 Notice: Use of undefined constant _RIJNDAEL_IV_ - assumed '_RIJNDAEL_IV_' in/var/sites/g/mydomain.co.uk/public_html/classes/Cookie.phpon line 80 At the moment my domain is waiting to be transferred and we are using a gridhosted domain. Could this be the problem? Should I contact my host? When I try to login it says employee or password not recognised. I've checked in phpMyAdmin and the employee is correct. But it wont send me a new password. As the wait time is 360mins I changed this to 2 mins temporarily but it still isnt working. It just tells me I need to wait 2 minutes even when I've waited 30 mins. Any suggestions welcome!

Has anyone got any ideas why the blocktopmenu module would be using up so much memory? We are still struggling with this issue. We have tried other menu modules but they are not as good and create other problems for us. If anyone can help please let me know.

Hi Vekia. Yes my colleague says she was editing the categories. She has explained what she was doing (just renaming and adding a new one). Her actions were perfectly reasonable so why did it wreak the site? I am really at a loss to understand how to repair it and get it live again. I've worked out that the problem is the blocktopmenu module. Simply by disabling it we can view and use our website again. Is there a repair I can do to this module or am I better off looking for another menu module? I would rather repair the existing module or do a workaround if possible.