Jump to content

musicmaster

Members
  • Posts

    5,423
  • Joined

  • Last visited

  • Days Won

    47

musicmaster last won the day on March 2

musicmaster had the most liked content!

Contact Methods

Profile Information

  • Location
    Netherlands

Recent Profile Visitors

30,622,313 profile views

musicmaster's Achievements

  1. Matching the tags is done by the browser. So I have no control over it and different browsers may even produce slightly different results. For the moment I have added a counter below the descriptions plus a red color when they are to big. Don't forget to refresh the browser cache (ctrl-F5 on the pc) when installing the new version.
  2. Thank you for the feedback. - I can add the product id to the error message - I can add a field size counter to the description_short field. However, there are two limitations: it won't work under TinyMce and it is not 100% accurate. Before submission the field is balanced - so that if you have an opening h1 or div tag without a closure that closing tag is added. That can increase the field size. - I am puzzled by your ps that not all records are processed. I cannot reproduce that. Can you provide more details? Is it the first or the last? Does it happen always or sometimes? Does it happen with specific fields? Does it sometimes concern more than one?
  3. This option shouldn't have been there at all. There is a special drop down menu option for the shop.
  4. I will look at the shop search. Just one other point about the speed. Many operations cause the need for re-indexation of products. That is dosed so that not too much is done at once. However, if you have big texts and many languages this operation could take too much time. You can try the option "skip indexation" in product-edit. The verbose option could be tried to see what queries are done.
  5. Sorry, I don't have a solution for that. I have no idea why this database is becoming slow. If someone else has a solution it would be welcome. Two suggestions: - Make sure that the database doesn't get too big. So truncate ps_connections, ps_guest, etc - Make sure that this database is the only database in your Mysql installation. The Mysql system tables are not indexed, so if you have more databases in one installation things can become slow quickly.
  6. Hi Constantin, Thanks for reporting the problem. I will fix. In the next release - that will appear in about a week it will be repaired. Regards, M
  7. images.somename.com is a different server. So your shop script doesn't have access to its file system and cannot copy images there even if it wanted to. You might consider installing a copy of your shop on the image server just for the image upload.
  8. You don't describe the context: does this happen in a shop that worked or is this a show stopper in a new shop? Link_rewrite is the field that is used to create the url. Seeing that you are using a non-latin (Persian?) alphabet my guess would be that one or more of those fields contain characters that are not allowed.
  9. At the moment it is not possible to install the latest versions of Prestashop under Windows. There is some bug around that is discussed here. This situation has already been for lasting two months. If you try you will get an error at 56%. If you look in the error log of the server you will see something vague about Swifmailer. So the latest Prestashop version that you can install under Windows is 8.1.2. Note that installing this version you may get the error "Warning: rename([]index.php.tmp,[]index.php): Access denied (code:5) in index.php on line 1338 ("error":false,"numfiles":28574,"lastId":29000)" with your path instead of the []. When that happens you should go to the root directory of the shop, rename index.php.tmp to index.php and then run the /install/index.php file of your shop in the browser. You may also get the OPENSSL_CONF error. That has been discussed elsewhere on this forum.
  10. Please enable debug mode and refresh the page so that you can see the error message.
  11. Since version 1.7.0 Prestashop stores settings like _DB_PREFIX_ in the file /app/config/parameters.php
  12. This image is just weird. Did you make a database with the name Prestashop on your server? Did you set the username and password that you set on the server?
  13. It can be both a module and cms. You should know. The first picture you show tells me nothing. You don't even check a module... If this was my shop I would have a quick text search for "guarantee" in both the files and the database of the shop. Never search for the ampersand: it could be encoded like & or &
  14. ISBN, like many other fields, is in the database defined as "default NULL". However, when those fields are saved in the backoffice they are always saved as empty strings when not set. This has become so common that the software gives warnings when such a value does have NULLs. ISBN is a field that was introduced in Prestashop 1.7. Most likely the software you were using was built for an older Prestashop version and never upgraded to cover this field. And as it was not defined when the ps_product records were created it got the default value of NULL.
×
×
  • Create New...