Jump to content

Paul C

  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Paul C

  1. You can edit the /modules/editorial/editorial.tpl file line that reads: {if $homepage_logo}body->$title|escape:'htmlall':'UTF-8'|stripslashes}" />{/if} to {if $homepage_logo}{/if} There isn't any other way of doing it I'm afraid. But you'll need to remember to also perform this change on any later versions of the editorial module you install i.e. during upgrades.... Paul
  2. As long as you copy all the data from your local copy to the remote copy, then there's no reason why it shouldn't work. Some important files/folders are: /img ; always make sure you copy the entire contents of this to your new server as this is where the product and category images are stored /themes ; you'll need to copy your theme over if you use anything but the unmodified default one. /mails ; if you've customised any of the email templates then you should copy this folder over to the new install /modules ; you may have added new modules in here and/or changed the code for exiting ones, so move these across too (the editorial module is commonly changed for example, via the back office.). /translations ; again if you've modified anything in here, then copy it over too. in /config/settings.in.php you set the "root" folder on your site for PrestaShop. Make sure that this is correct. Make sure you've altered the permissions on files as per the installation instructions; you can get a copy of this from the PrestaShop Download Page. If you post a link to your new site, then maybe folks having a look at it, can identify a specific problem you may have. Good luck, Paul
  3. There's two elements to the install. Well three if you count the database table additions, but they should be done by the module install routine. If the Admin tab doesn't show then I suspect that the file from the installation is perhaps in the wrong place. The file AdminAdverts.php (which is in admin/tabs in the archive) needs to go in the administration tabs directory on your server. You 'll have renamed the actual "admin" folder to something else of course as this is required for the backend security, so make sure you locate your own admin section and place the file in the tabs folder. The new Admin Tab has to be included in the menu system somewhere, This is done using the Tools-->Tabs option in the Back Office as per the diagram in the readme.html file. At this point if you go to the Adverts Tab you'll just get a Bad SQL error, as the database tables haven't been created yet. Once you've installed the module from the modules directory (it should be listed under "Advertising") the tables should be created, and returning to the Adverts tab in the Back Office should present you with an empty table, and the option to Add an item. Add one, entering all the data: Link: e.g. Http://www.ecartservice.net Description: A link to ecartservice.net Logo: [upload a suitable image to display for the above link] Once all these steps are complete it should display the image you've uploaded on your front page. Once you have several links in the table, you should configure the adverts Module to display them at random. Paul You may also need to check that the /img/a directory has been created and is writable!
  4. Yes you need to copy the files from the archive into the correct folder on your site. You can just upload each file instead of the whole lot if you prefer. I placed them in the correct directories to make it a bit easier! Using your example you just need to upload the file AdminAdverts.php from the admin/tabs folder in the archive to you /tabs folder on your site. Same with the others, although uploading the whole lot shouldn't harm what's there already... all the files are new. Once it's installed it won't do anyhting, of course, until you add some links & images from the Adverts admin panel. I would suggest using the two sample ones I've included in the media folder, just to test it out. Paul
  5. Works fine here: http://prestashop.ecartservice.net Could be an issue with the installation.... but don't have a lot of information to go on
  6. Just updated my site with another nice Module for PrestaShop. On-Page promotion of your own products, categories and static pages allow you to guide your visitors shopping experience.... Random Adverts and Callouts displayed on your pages This one includes an admin panel to configure your set of adverts/creatives and their associated links for display, and is slightly more complicated to install, although I've added the table creation code to the associated module install routine, which (if it works correctly!) should simplify things slightly. There's a readme.html contained in the archive. Have fun with it, Paul
  7. I like the sound of you being short of time ;-) Even something close could be worked with ! Paul
  8. Firstly you need to backup your existing site just in case - both the file system AND the database. Then you simply need to follow the upgrade instructions (you'll find a link to them on the download page). Remember to run the installer as instructed as this is required to upgrade the database too (it's not just a case of changing the files, parts of the database structure have changed too!). You'll need to keep copies of all of the original distribution ( files that you've changed for any purpose other than bug fixes, as well as the img and mails directories, and any modules that you added/edited. Changes that you still need to be in place will have to be reapplied manually to the new files in version 1.0. Paul
  9. These are "officially" signed ssl certificates and are essential if you're going to enable SSL on your public store. Self-signed certificates are useless to be hones, and worse than having no certificate at all. Some hosts provide a "proper" ssl cert as part of their package - others do not. Many believe that you don;t need an SSL certificate when you use external payment processors like PayPal (who use their own). I'm of the opinion that having one demonstrates your commitment to your customer's privacy and your system's security, so it is a definite bonus. Paul
  10. This is an interesting one. To be honest I think it's due to the way you're using attributes - that's a mighty big (and even if it worked), slow way of doing this! I think it would be better to add the attribute differently i.e. to only store the final selected date and time, rather than have all these different combinations. But how to do it? I'm sure I've read on here a propsal (which has been implemented in v1.1) to allow input of a value for an attribute. If that's the case then you would be able to use a nice javascript popup calander to select the date, then fill in the value for a single attribute i.e. Delivery Date and presto (or presta in fact) your problem's solved. I'll have a further think, as I'm sure this is something that will crop up again for other businesses. Paul
  11. The number per line for the layout calculations (nbItemsPerLine) is set in homefeatured.tpl (in modules/homefeatured) however it's unlikely that changing that value alone will work. I suspect that you'll have some serious work to do with the css too. At the very least you'll have to play with the width/height properties in : #center_column .products_block ul li and #center_column div.products_block a.product_image Among (possibly) several others! Paul
  12. I think that's wise mel62; that script looks a little basic and if it hasn't been updated for a while, probably misses out some stuff that's been more recently introduced. It was worth a try! If I get a spare slot in my schedule (sadly like everyone I've got to make a living too!) then I'll maybe have a look at writing something a bit more robust; we'll also see what appears in version 1.1 I guess. Paul
  13. I use beyond compare and it works for me, albeit a little convoluted. If you compare your current store code to the corresponding "official release" you'll see all the files you've changed. Save these somewhere. You can then do a compare of the old and new prestashop release code to find out if the files you've modified have changed between releases, if not just copy your modified version over the new version, and if they have compare the releases to see if your additions are affected and merge your changes into the new version. Paul
  14. Yuck. I hadn't looked at this before, but we need a better tool than this. Sadly I don't have the time to write one.... I've made the necessary changes to get rid of the database prefix - I'm assuming your osC tables don't have any. You'll still need to edit the following in db_mysql.inc.php to values which match your osC installation: var $Host = "localhost"; var $Database = "database"; var $User = "root"; var $Password = ""; Apart from that you can try running it on your osC server to see what it produces. Note that the generated sql will remove any existing products and categories from your current PrestaShop installation when you execute the generated SQL on your ps databse, and that it assumes that the prestaShop DB_PREFIX is set to "ps_" Paul osc2ps.zip
  15. mel62, Table prefixes aren't a problem really. Just have a search through the code to where the prefix is defined and remove them from all the table references - problem solved. I'll have a quick run through the code, and modify it to allow it to work on databases that don't use table prefixes. Will post it here shortly. Paul
  16. You should be able to change it in Tools-->Translations from the Back Office. In the "Modify Translations" box select "Modules Translations" from the dropdown, then the language you want to change. You'll be presented with a screen that displays all the text in the site that you can substitute for your own. Scroll down to the homefeatured module and change "featured products" to "featured events" and that should be it! Note that it's in lower case, but the text style capitalises by default. Paul
  17. The xml file is created and managed from the back office. Are you trying to edit the actual xml file? Paul
  18. Yes they will! I try and acourage folks to find alternatives to modifying files in anything other than their own theme directory (always copy the default theme, and rename it to work on rather than working on the default one, of course). If you makes lots of changes elsewhere, they'll all have to be redone come upgrade time.... you can't even assume that overwriting the upgrade with your changed files will work either; there could be other changes in the new versions that you'll need in your older files. It's always good to keep a note of anything (apart from the theme files) that you've changed! Paul
  19. Hmm. Manual order entry? That could be useful for folks who sell on eBay and want the order captured in their store..... Can you stop suggesting stuff!! My "To do" list has grown exponentially! ;-) Paul
  20. I think that expert help is on its way in your other thread Paul
  21. Actually the category_id is passed to the template, so all you'd need are the thumbnail versions somewhere, and you can display the images referenced by category_id...... e.g. if the images were named /img/c/menu-thumb-1.jpg (where 1 == the category id) Use smarty to add an image tag, by building the filename in /modules/blockcategories/category-tree-branch.tpl i.e. I think :cheese: Paul
  22. Fabrice, I've written a module that includes the whole Wordpress core into PrestaShop, and adds hooks to a sidebox (for the Latest News entries, and later will also be used for the Information Pages) and to the homepage, to display the dynamic content that way using non-template wordpress code (WP_USE_THEMES disabled). I'm not familiar with rapidweaver, so not sure if it has similar functionality? There's also a WordPress plugin to sort some of the issues from the WordPress side.... nothing is ever simple is it! The only "hack" I can't get around is adding the call to initialise WordPress. This has to be added to settings.inc, which is assumed to be changed; and shouldn't break an upgrade. To your problem.... If you can create an RSS feed of the articles you want on your PrestaShop site, then that could be included in a sidebox easily as dynamic links, but they would likely still take you to the external blog site. If it were me, I'd look at writing a script on the rapidweaver blog site that allows a remote server to get the content using cURL. Then you could write a PrestaShop module that goes and grabs the data, and displays it..... not trivial though, but an interesting challenge! Paul
  23. I use DreamWeaver, or the crimson (free editor). Paul
  24. The default template doesn't handle long product names in the featured products layout. The best way is to edit the css styles for it to make a bit more room... Paul
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More