Jump to content

pmates

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by pmates

  1. Please check that options to send messages to customer and send messages to merchant are turned on in the module "Contact form".
  2. Zdravim, Odpoved na vasu otazku sice nepoznam, ale s chybovou hlaskou ste zverejnili aj heslo vasho zakaznika do obchodu. Doporucujem kontaktovat zakaznika a doporucit mu heslo zmenit a nepouzivat ho ani inde.
  3. I have a question on what is the correct size of images to upload to the store, especially in relation to "Generate high resolution images" option. I read many posts about image sizes, but no one specifically mention this one. So, when uploading images, ideally the should be of size as it is defined in Design -> Image settings. If not precisely that dimension, at least the aspect ratio should be the same. PrestaShop will then anyway create several versions of the image for thumbnails etc. If "Generate high resolution images" is enabled, PrestaShop will generate one more set of images with double the resolution for retina displays. So if the image size defined in Image settings for product_default is 466x620px, should I upload images of size 466x620px or 932x1240px? I do understand that PrestaShop will handle almost any image with any size, but we are talking here about image sizes so that we achieve the best photo sharpness and no size distortion. Thanks in advance, for any experience on this.
  4. If you are looking for quick step-by-step guide on how to migrate PS1.6 to PS1.7, you can stop reading now. Spoiler alert, there is no such guide, which will guide you through your own migration. This is my story, with some lessons learned. My current store runs on PS1.6.1.23 and it works well. But still, I was planning to move to PS1.7 one day. I’ve been thinking about migration to PS1.7 for almost a year now. There are obvious reasons for doing so. On and off, I was trying to practice the migration. As probably everyone, I started with 1-click migration toll. I failed couple of times and eventually found a way for the upgrade to show “Upgrade successful” message. But those of you who did it, will know that 1-click upgrade is just a beginning. After upgrade, the layout of your page will be destroyed, backoffice will be crippled, modules will stop working and all sorts of issues will pop up. I’ve spent countless hours going back and forth. The scenario would be always similar. Move the store to development environment, prepare the store for upgrade, upgrade to PS1.6.1.24, upgrade to some version of PS1.7 most recently PS1.7.6.8 (upgrade to PS1.7.7.1 keeps on giving me errors) and then start fixing issues. Fix the access denied in the back office, fix the server error caused by blockrss module and a series of other issues. I already have 30-pages long manual on how to upgrade my store. But the end result is always the same. I would spend a full day, or even a weekend and in the end, tired and demotivated I would delete everything and call it a day and another failure. I’ve spent so much time already that if I had to pay myself, my store would go bankrupt. Now this is not to criticize PrestaShop, or its developers. I fully understand the complexity of migration to a new technology. And there is a wonderful community. Whenever you have an issue there is someone in community, who will help you. This is only to recognize that PrestaShop migration to a new major level is not an easy task and definitely not a 1-click matter. My frustration led me to completely crazy scenarios like upgrading the database of my store to PS1.7 and injecting it to a fresh installation of the store. Failure. But yesterday I found a way, which shows the light at the end of the tunnel. There are online services, which will migrate data from old store to a new store. So instead of upgrading your store, you simply take the critical data (products, orders, clients) and start fresh with a new store. I will not name any service. There are few and they seem to be suspiciously similar. Just choose such, which will allow you to run the migration several times. Anyway. All it takes is installing a new PrestaShop 1.7 on another domain and trying their demo migration. It worked beautifully for me. In a matter of minutes, I had perfectly running PS1.7.7.1 with few of my products (I did not complete the full paid migration yet). And the more I’m thinking about it the more it makes sense. Going between major versions changes everything. Over time we all have made many modifications to our stores. We installed modules, changed templates or modified the code here and there. But in the new version, all of that is probably different. If you had modules, which are suitable for PS1.7, you will be able to install them and configure in few minutes. If you did any modifications, it is possible that you will not need them in the new version. So for those of you, desperately struggling with upgrade of your store, consider this option as the way forward. It is a good opportunity to find a new theme for your store and start fresh. You will not lose your products, customers or orders. But you will start with a new, fully functional store, which you can again modify, customize and tweak as much as you want. Obviously, this will not be an option for everyone. But for some, it may be just the right thing to do. I’m with PrestaShop for already 6 years and never heard of such migration tools. If you are like me and never heard of them either, now you know
  5. Recently I experienced the issue of update/upgrade links not working after upgrading PrestaShop from 1.6 to 1.7. At almost every module I would receive a long error message including this key portion "../tools/pear/PEAR.php): failed to open stream: No such file or directory" In my case it turned out to be an issue of blockrss module. Since I don't use that module simply deleting modules\blockrss folder fixed the issue.
  6. Replacing ps_access table with a table from an empty store may look like it solves the issue, but it is not a fix exactly. Especially if you upgraded well running store with customizations and modules. Replacing the ps_access table will most probably fix your first symptom (not able to open Orders in Back Office), but may cause a lot of access inconsistencies elsewhere. For example, it also solves the problem of Shop parameters > General not being accessible). Here is more details using which you will be able to fix your access issues. Just for the record, I did it on my store, which was upgraded from 1.6.1.23 to 1.7.6.3 Access to menus depends to roles as they are defined in ps_authorization_role table. This table will look different for a fresh install and for upgraded store. To make your items work properly, you need to find desired roles in ps_authorization_role and assign those roles to access profile in ps_access. Access to menu items in Back Office is mostly controlled by roles with prefix ROLE_MOD_TAB_, defined in ps_authorization_role table. So to start fixing access rights, you need to identify, which ROLE_MOD_TAB_ roles are not assigned to SuperAdmin (id_profile = 1). It appears that SuperAdmin should have all the ROLE_MOD_TAB_ roles assigned to him. The query below will give you all the ROLE_MOD_TAB_ roles, that are not assigned to id_profile equal to 1, which typically is the SuperAdmin. You may want to double check that SuperAdmin truly has the id_profile = 1 in ps_profile_lang table. You may also want to double check in ps_employee that your user account has SuperAdmin rights. In this table, your account would normally have id_profile = 1. If not, you will need to adjust the queries below. Run this query (either in database manager or in Prestashop > Advanced parameters > Database). This list will give you all the roles, which you will need to manually assign to SuperAdmin. SELECT r.slug, r.id_authorization_role, CONCAT("(1, ", r.id_authorization_role, ")") AS 'Add this to ps_access table' FROM ps_authorization_role r LEFT JOIN ps_access a ON r.id_authorization_role = a.id_authorization_role AND a.id_profile = 1 WHERE r.slug LIKE 'ROLE_MOD_TAB%' AND NOT EXISTS(SELECT 1 FROM ps_access WHERE id_authorization_role = r.id_authorization_role AND id_profile = 1) ORDER BY r.slug Now add required roles to required profile(s). Each role will typically have four sub-roles (actions): Create, Update, Read, Delete. You will need to add all four of them. In my case, I will be adding roles to id_profile = 1 (SuperAdmin). If your SuperAdmin has different id_profile, you will need to modify all queries. By simple SQL command, you can add the missing records to the ps_access table (you will only be able to do this via database manager. The database manager in Prestashop does not allow INSERT command). The query above will already give you value pairs, which you can use in INSERT command Example: To insert one role, in this case role 311 to profile 1. INSERT INTO ps_access (id_profile, id_authorization_role) VALUES (1, 311) Or to enter multiple values (always in pairs - profile, role) INSERT INTO ps_access (id_profile, id_authorization_role) VALUES (1, 311), (1, 870), (1, 360), (1, 615) You can always come back to the query from above to double check that you correctly added roles to your profile. As soon as the role was correctly assigned, it will disappear from the query. So once the query gives you an empty list, you are done.
  7. Not sure, if my issue was the same as this, but I also had Could not perform action update for module undefined error when trying to update modules after upgrade of my shop from 1.6 to 1.7. In my case the issue was inconsistency between the real version of modules and versions recorded in database. The store keeps the list of all modules and their versions in table ps_module. I'm guessing that modules were updated during upgrade process, but correct values were not updated in the database. In my case the store would tell that I need to update 40 modules. For example it says that the module Best Suppliers should be upgraded from version 1.4.1 to version 2.0.0. But when I looked to the module folder itself, the module was already on version 2.0.0. Updating line for statsbestsuppliers (which is the folder name of this module) in ps_module from 1.4.1 to 2.0.0 fixed the issue. Going through all modules one by one can be a long work, plus guessing names of modules on top of it, but it seems to work. UPDATE 1: After many attempts to upgrade I came across another error, which seems to have solved the "module undefined" issue. As one of the comments suggested, the module Advanced EU Compliance (modules/advancedeucompliance) was causing some similar issues with updates of modules. After uninstalling this module before upgrade to 1.7, modules can now be properly updated. If you already upgraded to 1.7, deleting folder modules/advancedeucompliance may help the same way. The module should be completely uninstalled. Disabling does not seem to be enough. Don't ask me about explanation. This is pure try/fail experience.
  8. I had the same issue after upgrading from 1.6.1.16 to 1.7.4.4. The issue was clearly caused by 3rd party module. With the friendly URL turned on in [Traffic & SEO], clicking on [Modules & services] would redirect me to 404 - page not found. By turning the friendly URL off, I would be able to see the Symphony error (exactly the same as in the original post). I fixed it by deleting advancedeucompliance folder from modules folder at the server. I would have to search for AeucCMSRoleEmailEntity (the class from the critical error) to identify, in which module it was used. Then I simply deleted the whole module folder. Don't forget to click on the [LOG] tab in the Symphony error page to see full error details. By default it shows no details, only the following error. Compile Error: Cannot redeclare class AeucCMSRoleEmailEntity return Db::getInstance()->executeS($sql); After deleting the module folder, the [Modules & services] section started working instantly. You can then turn the friendly URL back ON.
  9. Hello Vekia, I believe the float: right; needs to stay in the css. By removing it, the menu above it stopped working. At least that was my case.
  10. Hi, I solved this by adding one more column to the ps_order_state table and adding few lines of code AdminOrdersController. The new column indicates that an order with specific state is closed (does not need my attention anymore). I turned on this indicator for statuses "Delivered", "Shipped" and "Cancelled". THen I added one more column to the order list with this field. Now I am able to filter based on it. I can either see all orders, or only closed orders, or the rest, which are in fact pending orders. Principles of adding a new column are nicely described in this aricle: http://nemops.com/filter-by-country-prestashop-order-list Applying those steps to this case makes it a lot easier. I am no coder, so my code is rough and dirty. Even setting up the status parameter must be done manually in the database. But it works. If anyone is interested in what I did, I'm happy to share. I will not be able to give any profesional support, but still it is something. Pavol...
×
×
  • Create New...

Important Information

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