ane76

just to let everyone know, i followed this solution, and was able to log in to the BO, long enough to do a roll-back. my 6-day nightmare with 1.7.7.0 is over 🙂

i tried it, and i get this error : Deprecated: array_key_exists(): Using array_key_exists() on objects is deprecated. Use isset() or property_exists() instead in /public_html/.........../src/Adapter/EntityMapper.php on line 99 it doesnt even let me put the user/pass

All TTL was 14400 (hosting is HostGator) i switched to 3600 and nothing happened. Also cleared cache and tried a second browser, still pressing the log button goes to the 1.7.7.0 Prestashop screen

I was on 7.2 originally. Tried 7.3, nothing changes, still after i enter user/pass i come up to a page showing just Prestashop 1.7.7.0 Tried 7.1 , same result. Tried 7.4 i get an error page I feel helpless locked-out of the Back Office 😞

Just upgraded to 1.7.7.0 to solve some minor issues i had, and now i cannot log into the BO, the eshop is in maintenance mode and all the above mentioned solutions do not work for me. Has anyone tried something else that worked ? Can someone tell me how i can revert to the previous version when i have no access to the BO anymore ? It is my opinion that you should have a message popping-up to warn people that is version can lock them out of the BO. If i knew it i would not try it during the holiday season 😞

I played around with back-ing up and restoring the TAX rules from a fresh clean install of 1.6.1.0 which didn't work either and eventually i tried importing the localization pack again....and it worked !! Didn't do anything else, just import localization pack and everything is back to normal ! Thanks for your reply, it made me look in the right direction !

It appears you are right ! It must be a bug in Prestashop version 1.6.1.0 I didn't delete the tax rule, i just disabled it and made a new one, added all countries as you said and selected the new tax rule in a product, voila ! prices on this product are back to normal (still missing the VAT included sign). Since the taxes only apply for within EU and the products are too many. Is there a way to make the original tax rules that stopped working, work again ? If not, Is there a setting that would treat the "visitor" as someone coming from the origin country of the shop and display TAX at all times before someone decides to register ?

No customization, never messed with the Tax Rules. Been leaving it at default for years now. First Prestashop version with issues there. Made a second install of my Prestashop to test, back-up/restored the products with tax rules etc, and everything works fine up to 1.6.0.14. As soon as i upgrade to 1.6.1.0 taxes are gone again. No themes or modules in this setup, just products and product categories.

Hi, Price Display Method: Tax Included No matter what i set, Tax Included or Tax Excluded, it just shows prices without tax and no mention about tax.

I have been using prestashop for a couple of years now and been through various versions. Taxes were always there regardless of the address and checkout. You could just browse the e-shop and look at the products displayed with the VAT. The GEO location was always off as it doesn't always work correctly and still, every visitor would see the GREEK taxes, as i am based in Greece. After they provided an address, if there were within EU they would have to pay the Greek taxes and if they were outside the EU they would not have the Greek VAT. Now, all taxes are gone for visitors together with the "tax included" sign.

Anyone any idea that could help ?

Hi all, I just upgraded to 1.6.1 and the prices shown to visitors are shown without vat and the "tax included" sign. The problem is that in 1.6.1 (as i also read elsewhere), the rollback function is not working either, so i m unable to rollback. Any ideas what should i do ? P.S. If someone registers and puts an address, prices are shown normally with taxes and the "tax included" sign. P.S.1 Checked the "Visitors" section, price display method is set at "Tax included" Thanks!

Have you succeeded in fixing it after all ? I tried your attached file but it isnt working for me :-(