oxyweb

Hi, Pretty much a noob with Prestashop (despite developing 3 sites) here is what I think so far, the idea being I give a perspective as a small business owner and semi-competent web designer. 1. Ambigious instruction. I hit my first stumbling block on the System Config page. I know. Not far. What does "You have to create a database" actually mean in context of the form below? Does it mean I have to create a database first in mysql or if I provide you with some details below you will go ahead and do it for me? It's the former (as far I can tell ). As "You have to create a database" wasn't much help I clicked the readme and from all that text only the following bit was somewhat useful (ideally what I needed to know what have been in the readme.txt Ah. Got ya. Could have saved me a click Suggestion: Rename the first portion of text something like: Before continuing, you'll need to go ahead and create a database in MySQL yourself. You can then enter that information into the form below... well something like that. 2. Database Server is not found. Please verify the login, password and server fields Pretty good error message and the chances are it is the Database server that it can't see so it's a shame it had to mention the login and password... IIRC prestashop will spit out a different error message if it can find the server and is having problems with the login\password combo. Suggestion: Clarify where the problem is specifically... I know you can! Edit: Turned out it was a password error. Grrr! 3. Installation Process page - Prestashop Ads There are some ads for the prestashop site... A little text saying something like "Whilst your site is installing, why not check out the full power of prestashop. Links open in a new page".. or something like that. 4. Front Office Screenshot... oh I wish the default template looked like the screenshot! 5. Backoffice first visit I get this message: For security reasons, you cannot connect to the Back Office until after you have: deleted the /install folder renamed the /admin folder (e.g. /admin123)871 Please then access this page by the new URL (e.g. http://www.yoursite.com/admin123)871 What's with the "871"? :/ 6. Hello Dashboard! <more to follow> 7. Compile cache if templates are updated Not only a time saver but a huge brain saver! All those times when something hasn't updated because you know what. 8. Damn that Memcache warning. and now we have APC too. 9. Why are you calling back to help.prestashop.com 10. Definiately seeing the pages load quickly after first attempt. E.g. 1.537s for Products page and then < 0.33s even after browser cache cleared

Hi, I'm a little bit stumped by this. When I return to my website from Google Checkout, I end up at https://www.xxxxxxxx...ack=history.php and the shopping cart is not empty and the order does not appear in Orders but does in Google's own checkout. There are no error logs in the gcheckout folder and I have checked my merchant key and id and made sure my https url is in the google sandbox sites settings. I'm using 1.4.8.2 so not sure if I need to follow PSCFI-1480... if so, do i add the htaccess to the root htaccess? A bit lost! My htaccess file incase its useful # .htaccess automaticaly generated by PrestaShop e-commerce open-source solution # WARNING: PLEASE DO NOT MODIFY THIS FILE MANUALLY. IF NECESSARY, ADD YOUR SPECIFIC CONFIGURATION WITH THE HTACCESS GENERATOR IN BACK OFFICE # http://www.prestashop.com - http://www.prestashop.com/forums <IfModule mod_rewrite.c> # URL rewriting module activation RewriteEngine on # URL rewriting rules RewriteRule ^([0-9])(\-[_a-zA-Z0-9-]*)?/[_a-zA-Z0-9-]*\.jpg$ /img/p/$1/$1$2.jpg [L] RewriteRule ^([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?/[_a-zA-Z0-9-]*\.jpg$ /img/p/$1/$2/$1$2$3.jpg [L] RewriteRule ^([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?/[_a-zA-Z0-9-]*\.jpg$ /img/p/$1/$2/$3/$1$2$3$4.jpg [L] RewriteRule ^([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?/[_a-zA-Z0-9-]*\.jpg$ /img/p/$1/$2/$3/$4/$1$2$3$4$5.jpg [L] RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?/[_a-zA-Z0-9-]*\.jpg$ /img/p/$1/$2/$3/$4/$5/$1$2$3$4$5$6.jpg [L] RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?/[_a-zA-Z0-9-]*\.jpg$ /img/p/$1/$2/$3/$4/$5/$6/$1$2$3$4$5$6$7.jpg [L] RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?/[_a-zA-Z0-9-]*\.jpg$ /img/p/$1/$2/$3/$4/$5/$6/$7/$1$2$3$4$5$6$7$8.jpg [L] RewriteRule ^([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(\-[_a-zA-Z0-9-]*)?/[_a-zA-Z0-9-]*\.jpg$ /img/p/$1/$2/$3/$4/$5/$6/$7/$8/$1$2$3$4$5$6$7$8$9.jpg [L] RewriteRule ^c/([0-9]+)(\-[_a-zA-Z0-9-]*)/[_a-zA-Z0-9-]*\.jpg$ /img/c/$1$2.jpg [L] RewriteRule ^c/([a-zA-Z-]+)/[a-zA-Z0-9-]+\.jpg$ /img/c/$1.jpg [L] RewriteRule ^([0-9]+)(\-[_a-zA-Z0-9-]*)/[_a-zA-Z0-9-]*\.jpg$ /img/c/$1$2.jpg [L] RewriteRule ^([0-9]+)\-[a-zA-Z0-9-]*\.html /product.php?id_product=$1 [QSA,L] RewriteRule ^[a-zA-Z0-9-]*/([0-9]+)\-[a-zA-Z0-9-]*\.html /product.php?id_product=$1 [QSA,L] RewriteRule ^([0-9]+)\-[a-zA-Z0-9-]*(/[a-zA-Z0-9-]*)+ /category.php?id_category=$1&noredirect=1 [QSA,L] RewriteRule ^([0-9]+)\-[a-zA-Z0-9-]* /category.php?id_category=$1 [QSA,L] RewriteRule ^([0-9]+)__([a-zA-Z0-9-]*) /supplier.php?id_supplier=$1 [QSA,L] RewriteRule ^([0-9]+)_([a-zA-Z0-9-]*) /manufacturer.php?id_manufacturer=$1 [QSA,L] RewriteRule ^content/([0-9]+)\-([a-zA-Z0-9-]*) /cms.php?id_cms=$1 [QSA,L] RewriteRule ^content/category/([0-9]+)\-([a-zA-Z0-9-]*) /cms.php?id_cms_category=$1 [QSA,L] RewriteRule ^page-not-found$ /404.php [QSA,L] RewriteRule ^address$ /address.php [QSA,L] RewriteRule ^addresses$ /addresses.php [QSA,L] RewriteRule ^authentication$ /authentication.php [QSA,L] RewriteRule ^best-sales$ /best-sales.php [QSA,L] RewriteRule ^cart$ /cart.php [QSA,L] RewriteRule ^contact-us$ /contact-form.php [QSA,L] RewriteRule ^discount$ /discount.php [QSA,L] RewriteRule ^guest-tracking$ /guest-tracking.php [QSA,L] RewriteRule ^order-history$ /history.php [QSA,L] RewriteRule ^identity$ /identity.php [QSA,L] RewriteRule ^manufacturers$ /manufacturer.php [QSA,L] RewriteRule ^my-account$ /my-account.php [QSA,L] RewriteRule ^new-products$ /new-products.php [QSA,L] RewriteRule ^order$ /order.php [QSA,L] RewriteRule ^order-follow$ /order-follow.php [QSA,L] RewriteRule ^quick-order$ /order-opc.php [QSA,L] RewriteRule ^order-slip$ /order-slip.php [QSA,L] RewriteRule ^password-recovery$ /password.php [QSA,L] RewriteRule ^prices-drop$ /prices-drop.php [QSA,L] RewriteRule ^search$ /search.php [QSA,L] RewriteRule ^sitemap$ /sitemap.php [QSA,L] RewriteRule ^stores$ /stores.php [QSA,L] RewriteRule ^supplier$ /supplier.php [QSA,L] </IfModule> # Catch 404 errors ErrorDocument 404 /404.php <IfModule mod_expires.c> ExpiresActive On ExpiresByType image/gif "access plus 1 month" ExpiresByType image/jpeg "access plus 1 month" ExpiresByType image/png "access plus 1 month" ExpiresByType text/css "access plus 1 week" ExpiresByType text/javascript "access plus 1 week" ExpiresByType application/javascript "access plus 1 week" ExpiresByType application/x-javascript "access plus 1 week" ExpiresByType image/x-icon "access plus 1 year" </IfModule> FileETag INode MTime Size <IfModule mod_deflate.c> AddOutputFilterByType DEFLATE text/html AddOutputFilterByType DEFLATE text/css AddOutputFilterByType DEFLATE text/javascript AddOutputFilterByType DEFLATE application/javascript AddOutputFilterByType DEFLATE application/x-javascript </IfModule>

Cool. It looks like that module contents are displayed in the wrong div. if I move the following html to under the header div as opposed to the header>header_right it appears reasonable well with a bit of css it will look perfect. <div style="" class="block" id="html_block_left"> <br><img width="909" align="middle" height="80" src="http://www.cleanmitts.org/shop/indexad1.jpg"></div> So erm, how do you go about it? Are you ok to edit the tpl file or even before that see if it can be moved in LiveEdit mode. Why it happened? Have you been editing the css a lot? Does it happen with a brand new default template? None the less I hope this points you in the right direction.

Hi CM, Looks like a html\css issue at first glance. can you enable your shop so we can look at the html?

Hi Zuzu, There are so many different ways you can approach this but before I mention how I would do it, I will just ask one question! have you tried disabling the module in the ps_module table or remove it from the modules dir (even fi that means removing them *all* and then putting them back in the folder in small numbers? I know you've said that you've tried all sorts but just double-checking! If you have already then yes as long as you have a copy of the database and files you are good to go *but* the issue might reappear since you using the same files and db again. Rather than delete folders, just rename the current prestashop folder via FTP and rename the database too. Good to have these just in case it goes a bit quirky. Hope this helps.

Thank you for the quick response Mike. As long as there is no "callback" then I'm happy.

Hi, Check the server name as in my case the mysql server is stored separate from my html root. Log into myphpadmin and check the server name from there. (Pink boxes below)

Hey Patric, Could you provide more info on why this is? Thanks

Anyone else agree there are just too many ambiguously named subforums which do nothing to help categorise the content and amke it difficult to discus and help people? I have a feeling that I am not the only one who gets somewhat overwhelmed with all the locations to find new content or new users who need help. e.g. Installing PrestaShop / Upgrading PrestaShop / Configuring & using PrestaShop / Integration really should be in one forum Development and Theming should all be in one subforum There's also other merges that really could help improve the level of activity for Prestashop. Thanks for listening!

Hi, I don't believe it can be done from the back end but the following work is what I do: in your themes/themenamefolder/ look for authentication.tpl and order-opc-new-account.tpl. Within these files you will find the following twice in authentication.tpl and order-opc-new-account.tpl, either you can delete it or better would be to comment it out with html comment tags. <p class="select"> <span>{l s='Date of Birth'}</span> <select id="days" name="days"> <option value="">-</option> {foreach from=$days item=day} <option value="{$day|escape:'htmlall':'UTF-8'}" {if ($sl_day == $day)} selected="selected"{/if}>{$day|escape:'htmlall':'UTF-8'} </option> {/foreach} </select> {* {l s='January'} {l s='February'} {l s='March'} {l s='April'} {l s='May'} {l s='June'} {l s='July'} {l s='August'} {l s='September'} {l s='October'} {l s='November'} {l s='December'} *} <select id="months" name="months"> <option value="">-</option> {foreach from=$months key=k item=month} <option value="{$k|escape:'htmlall':'UTF-8'}" {if ($sl_month == $k)} selected="selected"{/if}>{l s="$month"} </option> {/foreach} </select> <select id="years" name="years"> <option value="">-</option> {foreach from=$years item=year} <option value="{$year|escape:'htmlall':'UTF-8'}" {if ($sl_year == $year)} selected="selected"{/if}>{$year|escape:'htmlall':'UTF-8'} </option> {/foreach} </select> </p> It also appears in identity.tpl which is the user's profile once they have registered. you may wish to leave that in. Don't forget to Foce Compile Smarty in Preferences > Performance.

Ahhh the 'Layered Categories Module' aka the a**hole module.

Hi Genet, Make sure you're connecting using the correct mode for PayPal. If you're testing Paypal then the PayPal module should be set to use the Sandbox Mode. e.g. This is my sandbox mode:

Hi, Essentially an advert\promotion for all the things that are on clearance. A bit like Amazon: That 10% off fashion is a promo but I'm sure they could have easily put a "Clearance Items" image there instead. Hope that makes sense.

I was thinking about it, and, as far as I can tell, Prestashop doesn't give each category a unique CSS selector ID so you can't really actively select one and tell the browser to render it differently. The only thing I can think of (without bashing the database to pieces) is maybe using one of those HTML block modules (Link Block module might work otherwise a free html block module) and setting below the rest of the categories. I think you can hide the clearance category then if you wish - but I would say that you should consider making Clearance into a promotion