rabox66

Hi, ich hab das Thema über Weihnachten wohl vergessen. Jetzt bin ich wieder dran. Die Stellen in Woo-Germinized hab ich inzwischen gesehen. Zur übersetzung habe ich aber eine Frage:

Ich müsste doch eigentlich im Code von Woo-Germaized die Stelle finden, wo die Checkboxen definiert sind und nachsehen, ob der Codeteil für eine übersetzung vorgesehen ist. Falls ja, müsste ich nur in Loco-Translate bei Woo-Germanized den engl. Text hinterlegen. Falls nein, hab ich aber ein Problem, weil ich müsste das Plugin aufbohren, den Teil übersetzbar machen und würde dabei die Updatef?higkeit des Plugins verlieren.

Liege ich mit meiner Beschreibung ganz falsch?

Danke für diese Auskunft, ich frage also bei Polylang. Nur kurz: Wo finde ich denn die hinterlegten Text in WG-Germanized?

Hi,
thank you for your answer, but the problem is different:
– When the plugin is activated the Responsive Menu does not work
– When the plugin is deactivated the Responsive Menu does not work
– When the plugin is completetly deinstalled the Responsive Menu works again.

Therefore it MUST be in relation with Mailpoet 3. But how?
Cheers
Raphael

Danke für den Tipp. Das Rechtliche habe ich aber nicht bedacht.

OK, now also the producer can see the problem. :))) Very good. Thank you for participating.

Now I only have to convince him that an update will be necaissairy. If a theme shows bugs on the site of the producer it is not very convincing. ??

@?Guido,
yes I have troubles on my site aswell. But I did lots of modifications on my site. Therefore I only show the problem on the site of the producer in order to convince him, that the problem is because of something he is responsible.

Up to now he sais, that he cannot see any problems. Therefore he refuses any assistance. As we can see now very clearely, the problem exists.

@?bcworks:
I tried the dark theme without any additional plugins and the problem remains. I cannot try the booking-tool with any other theme, because it is part of the theme.

@?Guido: Thnks a lot for doing the tests! That helps me in arguing with the support who cannot find any problem. (Only to point it out: It is a payed theme, not a free theme.)

A plugin or theme conflict is not possible since this is the website of the producer. But thank you anyway. By answering my question you also agreed that this problem exists. That was the main part of my question, because the support which is offered by the producer ( goodlayers.com ) says, that my problem is imaginative only. He cannot see it.

OK: To make it clear: At least two people in the forum can see the bug, The support says, there is no bug.

Hi lorro,
thank you for the answer. Now I know where that piece of code is located. I will work on it later, so I cannot tell you now, whether your proposition worked or not.
Thanks
Rabox

Thank you, works perfect!

Thank you. I could resolve the problem with that answer.

Do you have a link with furtcher information about the console?

Thank you
Rabox

Hi Averta,
thank you for the information. I changed now the transition speed up to 40. I can see differences, but it is not exactly what I want.

I imagine that the slider should offer two different periods which are scalable independently. But in my case those two periods seem to be connected.

1) The time each slide is shown,
2) The time two slides nead to exchange places.

I would like to put 1) to aproximately 4sek and 2) to 0.5sek. After seeing the result I would like to go on with further adjustment.

Best
Rabox

Thank you for that fast answer. YES, ist worked with the jQuery update. ??

Hi borisv, as I did not receive any answer, I want to point out, that offcours I did everything that is explained in your link. It is definitely the “Ultimate Member” Plugin that causes the troubles since WP 4.7 is installed on my site.

So how do we go on? I suppose I am not the only one with this problem.
Thanks
rabox

Yes, I realize now, that the problem occurded directly after the update. The site is active since one month and everything worked well. Directly after the update the problems started. They stop after deactivating the plugin. As far as I can see, the plugin is not ready for 4.7. So the only way of resolving the problem is waiting for a plugin-update.

@Spport: Do you agree?