[Malta]

A quite important part of the allover compatibility with woocommerce 3.0.x (actual 3.0.7) to me seems the after update WC message “Actualización de datos de WooCommerce – Necesitamos actualizar la base de datos de tu tienda a la última versión.” = “We need to update/upgrade the database of your shop to the latest version”.

So my question is if this is supposed to run smooth without causing any issues or are you aware of clients that had problems here? Would you strongly recommend to fully backup the databse + wp-content folder before performing this action or would you consider this being harmless? Thanks.

[Malta]

No need for doing a video…
another use had the very same problem http://www.swiftideas.com/forums/topic/revolution-slider-mobile-landscape-view-problem/ and still I could not see or find out how you helped him solving the sissue.

For the replication:
1. Take any page you wish with some more different elements and add the “Rev/Layer/Master Slider” element to it and just let the page option under “Meta Options – Page Header / Slider – Revolution Slider” EMPTY. SAVE PAGE!
2. View your page with Google Chrome or Mozilla Firefox or any TABLET
TABLET: Switch from vertical to horizontal and you will see the issue (slider is not responsive)
BROWSER: Size your browser window to be quite small AND NOW you start clicking on the maximize/restore size button (which is next to the X/close window button) – click it again and again… you should see the issue !!

Can you please confirm?

PS: I added two pictures.

Attachments:

You must be logged in to view attached files.

[Malta]

This reply has been marked as private.

[Malta]

Meanwhile I investigated the issue quite a bit and this is what i found out:

There seems to be no responsive issue in three cases: 1) if you create/insert any revlution slider to a brandnew page with just its full shortcode (better doing it in HTML mode). 2) if you decide to use the PAGE option under “Meta Options – Page Header / Slider – Revolution Slider” and just put in the slider alias (no full shortcut possible here). 3) Probably also no issues, if you set the PAGE option “Meta Options – Page Header / Slider – Page Header type” to “Naked” (<- even if you make use of the “Rev/Layer/Master Slider” element”

However, if you take any other NORMAL PAGE full of some rows, columns (and some other normal elements) and you add a revolution slider by using the given “Rev/Layer/Master Slider” element you will have and are able to observe the described issue! I can only guess that this error must be related to something within the Swift Framework not updating sudden big resolution changes.

As for the “workaround” by using case number 2 (see above) you are limited to display 1. only one slider and 2. only on the top of the page. At the moment I dont see the “Rev/Layer/Master Slider” element working the way it should… that you can add multiple sliders or on different places other than the top of the page without having these responsive issues. Please, are you able confirm my observations? Thanks.

[Malta]

Guess what… the trick was to first “clear(flush) the existing cart” in order to take effect on refreshing the mobile menu.
!! A normal cache and browser reload does not work here !! … how can someone know or suspect this kind of behaviour??

Thanks anyway, issue resolved, ticket closed.

[Malta]

Thanks again. Setting topic to “resolved”.

[Malta]

Thanks a lot for your very fast reply and help!
You seem to be right with that SEAR plugin. At the moment everything is back to normal.
Seur is a spanish national-wide delivery service company and I will inform them about their error.

[Malta]

This reply has been marked as private.

[Malta]

Thanks, that worked.

[Malta]

If you refer to atelier/language/es_ES.po … yes, that is where we already found them and they are both correct:

#: swift-framework/core/sf-header.php:1089
#: swift-framework/core/sf-woocommerce.php:619
#: swift-framework/core/sf-woocommerce.php:703
#, fuzzy
msgid “Your cart is empty.”
msgstr “Ver su cesta de la compra”

#: swift-framework/core/sf-header.php:1215
#, fuzzy
msgid “Your wishlist is empty.”
msgstr “Su lista está vacía.”

However, the english strings (see screenshots) still keep appearing. Regarding wordpress and theme translation we understand that it should be enough to switch the wordpress language itself (we did so to spanish) like described here: http://swiftideas.com/documentation/2014/05/26/translation/
Or is there anything else (beside just wordpress itself), something within the theme that needs to be switched in order to really make use of this “es_ES.po” file? Also we searched the whole database for these two strings without any success. So we still wonder where we need to change these two strings. Maybe does the use of a child-theme can cause such strange behaviours to language files?