goosedesign

Does anyone know how to achieve this? My shop has two top level categories, "Hire" & "Buy". Well I suppose they are children of "Home" so not absolute top. Each of these has several sub-categories with products, but no sub-sub-categories. What I want to do is replace "Buy Now" with "Hire Now" in product-list.tpl, where the product's category is a child of "Hire". Is this possible? If it's not, at a push, I could check against the entire array of sub-category IDs, but I don't know what the syntax would be for that? I guess I would have to add a function in to a controller somewhere? Many thanks for any advice.

Thanks so much Bellini & Nemo, that's just what I needed to know.

It probably goes without saying that this site is in desperate need of upgrading, but in the mean time, the hosts are discontinuing PHP 5.2, which is what the site is currently running on. Until we get around to upgrading the website, can anyone tell me what is the highest PHP version that this old version of Prestashop can run on? Any advice very much appreciated.

Thank you El Patron! I've decided to stick with 1.5.6 for now as (unlike the included module and a third party PayPal Pro one I've used), the Prestashop PayPal Pro module appears to work perfectly. Bellini, thank you for the advice, but I have been through the extremely time consuming trial and error process many times in the past with other sites and simply don't have the time right now, which is why I asked the question(s).

Hi Robin Thanks so much for that. But I get the error: "Notice: Undefined index: cms…" and "Notice: Trying to get property of non-object…". What have I done wrong?

Hi, I'm looking for advice to hopefully spare me frustrating and time consuming unnecessary work! I have just locally upgraded an old site from 1.3 to 1.5.6. It seems fine so far, except that I still have to install PayPal Pro and a Mailchimp module of some sort. The upgrade to this point has been painful because it required a total overhaul of the template. What I'm wondering is should I upgrade to 1.6 while I'm at it? I only went to 1.5.6 after reading a suggestion somewhere on the forum that 1.6 was still too buggy. The client needs to be online with it pretty soon so I can't afford to spend a lot of time fighting bugs. I suppose the questions are: How stable is 1.6 looking so far? Will I have to make more template mods to get from 1.5.6 to 1.6? What are the options for PayPal Pro with 1.6? Is it just the hosted solution with the free module? The official PayPal Pro module (http://addons.prestashop.com/en/payments-gateways-prestashop-modules/5314-paypal-pro.html?utm_source=v1trunk_api&utm_content=paypal%20pro) says it's only compatible up to 1.5.6. On the subject of the above module, if I don't upgarde to 1.6 and use that module, is it good? I can see it has 4/5 stars from 37 reviews, but not sure how useful that is without actual feedback. Thank you so much for any suggestions!

Thanks Robin. I'm a designer who just dabbles in PHP and that process is just a bit beyond me. I managed it somehow in a previous version by copying and pasting code, but I fear I would need to really understand what I'm doing these days!

Thanks Vekia, that's ideal for small quantities of text, but I'm talking about a situation where you want the full features of the editor, probably quite a large body of text, and the ability for an administrator to easily edit it. The contact form template is a classic example, and the one that's plaguing me right now. If I can create a CMS page called "contact" and call it in the contact template, just before the form, we can include all kinds of information including address, telephone numbers, hours of operation, even images if necessary. If anything needs to change, it's a simple matter for the site admin to edit a CMS page. PSFever.com, I would love to know how to call a predefined CMS page in the contact form template in PS 1.5.

I don't know if this is the right place to put this, but it's worth a shot. There are many situations where I find limitations in the basic Prestashop software could be overcome by including a CMS page inside another template. One example is the contact form template, which on most sites really needs much more information than a single line of text before the form. In a V1.3 site I was able to figure out how to do this, but in subsequent versions it no longer works and seems to be very difficult to achieve. It would be fantastic if there was some sort of global variable that could be used to easily pull the content of any given CMS page in to any template. Or maybe somebody knows how to do this in V1.5?

Most of my upgrade problems turned out to be caused by insufficient resources in the PHP configuration file. I bumped it all up in MAMP and the auto upgrade module worked.

Oh wow Divyesh, thank you so much! That works perfectly.

I made a ridiculously simple little module to display the contents of a pre-defined cms page in a box on the shop home page. The admin can use use that page for promotions and as a general notice board. Unfortunately it no longer works after upgrading to 1.5. Can anybody tell from the code what might need to be changed to make it compatible? Here's the PHP <?php class BlockPink extends Module { function __construct() { $this->name = 'blockpink'; parent::__construct(); $this->tab = 'Blocks'; $this->version = '0.1.0'; $this->displayName = $this->l('Pink Box'); $this->description = $this->l('Adds a pink box to the home page showing text from the "pink box" page in the CMS'); } public function install() { parent::install(); if (!$this->registerHook('home')) return false; } function hookHome($params) { global $smarty; $query = "SELECT * FROM ps_cms_lang WHERE id_cms = '7' AND id_lang = '1'"; $result = mysql_query($query); $row = mysql_fetch_array($result); $cms = $row['content']; $smarty->assign(array( 'cms' => $cms)); $errors = array(); return $this->display(__FILE__, 'blockpink.tpl'); } } And the template: <div id="pink_block"> {if $cms} {$cms} {else} {l s='This page does not exist.'} {/if} </div> Many, many thanks for any light anyone can shed on this.

I have the same issue but with manual rather than auto upgrade (which just failed completely). Is there a similar bug somewhere in the install/upgrade folder?

Damn it I forgot to follow the topic. You would think it would be automatic to follow a thread I started. Thanks for the replies. The thing is that I have the impression that this site is behaving differently from most others and I don't know why. The developer of the PayPal Pro module says this hasn't happened with other sites and has no suggestions, so I don't think it's anything I can change in the module itself. I just hoped somebody else had encountered the same thing as it affects the standard PayPal module as well as the third party Pro one.

Thanks – where would I do that? I don't see an option to define a return URL either for PayPal or PayPal Pro. Surely as SSL is enabled for the shop, the return URL should automatically be https?