Jump to content

KarZan

Members
  • Posts

    26
  • Joined

  • Last visited

Profile Information

  • First Name
    Kari
  • Last Name
    Kniivilä

Recent Profile Visitors

221 profile views

KarZan's Achievements

Newbie

Newbie (1/14)

3

Reputation

  1. Hi The problem with this is you do not get products which have no combinations. At least I have products with no combinations as I have products with one or two combinations. My earlier post on the other hand lists those also. But in my post there are somewhat more fields AND the id_lang needs to be edited to proper value.
  2. I have not had the possibility yet to upgrade to 1.6.1.14 so do not know if it would fix this. I do not know if server is configured to use varnish external caching since it is webhosting. PHP version I think I mentioned earlier but it is 5.6.30. No extra caching activated. All caching has been disabled. It would be odd if TinyMCE settings would have changed since as I also mentioned before I have put up a fresh 1.6.1.13 installation and still the text color addition causes error on any product. Anyway I need to test the 1.6.1.14 upgrade at some point when I have the possibility. EDIT: I have not had the possibility to try the upgrade and the problem is gone??? I have not done anything. My only conclusion is there was something in the hosting that caused the problem in the first place and some change there has fixed my problem. I noticed PHP version is now 5.6.31 which is one minor bigger. And MySQL is now 10.1.24-MariaDB which is three minor versions higher. So not big changes. And now I installed mailchimp module and when updating contacts to mailchimp I still get the same error. Which seems odd and looks like it would have something to do with PHP settings. But this happens only on the first time using the module. So I will have a go with upgrading to latest 1.6 version on my test shop and see what happens
  3. I agree it is not the DB difference. As I posted last I installed new 1.6.1.13 instance and then just created a new product. Nothing fancy just a simple product with only mandatory fields entered. Then after creating the product I edited it and put one word in desription and changed the colour of the text to red (ff0000). Saving the product gave me an error telling me I do not have rights to edit index.php file in the admin folder. Removing the colour red definition allowed me to save changes. So to mee it looks like there is an actual bug but would like to hear if someone else could confirm it.
  4. I have now double checked that on a vanilla 1.6.1.13 setting text color on a product description text using the in built rich text editor tools gives: "You don't have permission to access /admin_folder/index.php on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request." Can anyone confirm this?
  5. Some additional information. I installed a test shop with the same version I now have in production. I copied products data from the production to this new installation. Now I have a bit different situation. If I edit one of those copied products I get "You don't have permission to access /admin/index.php on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request." But I can create a new product and edit it just fine. So obviously it should not really have anything to do with the permissions? So my test shop is 1.6.1.13 with default modules and default settings. Just copied the images and the following tables over: ps_attribute ps_attribute_group ps_attribute_group_lang ps_attribute_group_shop ps_attribute_impact ps_attribute_lang ps_attribute_shop ps_category ps_category_group ps_category_lang ps_category_product ps_category_shop ps_feature ps_feature_lang ps_feature_product ps_feature_shop ps_feature_value ps_feature_value_lang ps_image ps_image_lang ps_image_shop ps_layered_category ps_layered_filter ps_layered_friendly_url ps_layered_indexable_attribute_group ps_layered_indexable_attribute_group_lang_value ps_layered_indexable_attribute_lang_value ps_layered_price_index ps_layered_product_attribute ps_manufacturer ps_manufacturer_lang ps_manufacturer_shop ps_product ps_product_attribute ps_product_attribute_combination ps_product_attribute_image ps_product_attribute_shop ps_product_lang ps_product_sale ps_product_shop ps_product_supplier ps_product_tag ps_specific_price ps_specific_price_priority ps_stock_available ps_supplier ps_supplier_lang ps_supplier_shop At the moment it looks like it would have something to do with the products data. So I removed all text from both short and long description fields and was able to save the change. Then I copied the same text without any formatting and was also able the save the change. Then using the rich editor I changed colour of one word and was not able to save anymore. I can bold the word and make it a heading but it seems I cannot change the colour. And there are some products with table of sizes I had to remove formatting from the table to be able to save the changes.
  6. I believe I have said it a couple of times already. I am not getting 404 or 500 or any other webserver error message. I am getting prestashop "page not available" page. There is header and footer from my shoo and on the middle text saying "page not available". So from the web server point of view there is no error.
  7. I have no access to actual server error logs. Server access logs has nothing peculiar which could give a hint of what the problem is. When comparing a succesfull product update to nonsuccesfull one there is only three GET statements and no POST statements in the unsuccessfull case but when successfull there is two POST statements and over 10 GET statements. I am not getting 404 from the server but prestashops own "page not available" page. And thus it is understandable that there is no error on the server logs. And I would like to stress that all was working with 1.6.1.1 but just after upgrading to 1.6.1.13 this emerged. And I have now noticed that some products can be updated and some cannot. I have also noticed that in some cases by removing description text the update goes through but it does not apply always. Sometimes there is nothing in description and it still does not work.
  8. Cache has been disabled already and deleted both from bo and manually on the server. Tried different browsers in different OS in different computers. Even android. Also regenerated .htaccess already. No change. And to make things more weird some products can be edited???
  9. Just noticed I end up in page not found also when trying to update email translations. If that helps anyway. Maybe it has nothing to do with the products anyway?
  10. Changed max_execution_time but it had no effect. I did not think it would since the page not available comes immediately after clicking save. Also I activated debug mode but there is no error messages. Then I made a test installation of totally new PS 1.6.1.13 and copied over the database from nonworking to this new installation. I know it should not be done since the systems are not quite identical. But I could reproduce the problem. Thus I still do believe the problem is in database. Maybe I should have upgraded like every minor change separately So my question still remains: Is there any documentation on how 1.6.1.1 and 1.6.1.13 databases differ. Or better yet how has product handling changed.
  11. I do have created a post of my problem https://www.prestashop.com/forums/topic/610263-error-updating-old-products-after-1-click-upgrade-1611-16113/ I am using default theme. I do have some extra modules like for payment. But I've got almost a vanilla installation. I am wondering if it could be that I do not have English at all only local language (Finnish). 1) This I have not yet tried 2) Done but did not help 3) Configuration - PS 1.6.1.13 memory_limit = 512M max_execution_time = 30 max_input_time = -1 upload_max_filesize = 2M post_max_size = 8M max_input_vars = 10000 allow_url_fopen = on safe_mode = off cURL yes mod_rewrite ? php 5.6.30 (php-fpm/opcache/fast-cgi do not know) server firewall is what it is with my provider but any time there has been any problems they have reconfigured it Prestashop services. Prestashop uses several external services. No knowledge mod_security = off mySQL 10.1.21-MariaDB-cll-lve So as you can see there are differences. But everything was working fine before upgrade from 1.6.1.1 to 1.6.1.13
  12. I just upgraded 1.6.1.1 to 1.6.1.13 and have had mostly problems. The most biggest is I can not update old products. It just ends up to a page not found. Also it seems bamkwire email does not anymore contain the actual bank information and thus the customer does not get any relevant information. So if you decide to upgrade make a copy of your store and upgrade that and then test EVERYTHING. I was stupid not to test everything. Just made a quick "everything seems to work" test and now I am in trouble. I noticed the problems a few days after and I could not just restore the old store.
  13. Does anyone have any knowledge what is the difference between 1.6.1.1 and 1.6.1.13 databases? If I restore the code of 1.6.1.1 does it work with the DB? I was planning to downgrade from 1.6.1.13 to 1.6.1.1 so I would retain everything that has happened since I made this unfortunate upgrade.
  14. And just as additional information. If the description field is empty in the old product it does not work. And it cannot be fixed by adding something to the field. Odd as I said.
  15. Thanks for the hint but did not help. I did notice though that removing text from description (leaving only the short description) it made the saving work. It seems like there is some problem in the data in the field although I can not find out what. I have a table in the old products description field but if I empty it and create a new table it works. I can not see any extra characters in the html code either.
×
×
  • Create New...