alFrame

Great plugin. Exactly what I was looking for.

But, I actually have the same problem.

See here: https://snipboard.io/1HMOyv.jpg
HTML here: https://snipboard.io/MvI7gj.jpg

It seems you insert your code inside the same div with the quantity and the add to cart button. Maybe it’s because it’s a variable product?

IMHO the plugin should add a separate div or table with 100% width so the quantity and the add to cart button are below the text input field.`

• This reply was modified 3 years, 1 month ago by alFrame. Reason: Added a screenshot of the html code

Strange enough logging into my site this morning I did not see the warning anymore. I also don’t see the warning after ticking all the checkboxes. And also not after updating the plugin.

Sometimes it’s magic!

Thank you for reacting so quickly.

Problem resolved. The error sat, once again, 2 feet in front of the screen.

Sorry!

Thank you very much for your elaborate answer. That really helped. Looking into the tag cloud now. Will probably have questions ??

Sorry for double posting. But I figured out that I have to activate and set the mapping on “Tags” to “2#025:Keywords”.

But I still have to enable the mapping on every single image “<- Click To Toggle”.

Is there a way to enable this by default for every upload so the tags are mapped to images? And how would I go about exposing the tags in form of a tag cloud in the front end of the website?

Thanks again!

v2 works perfectly now!

Thanks man! Cool thing.

I wish there was a way to change the darkening and the font properties in general of the “Before” and “After” that appears when hovering without adding css ??

Cheers!

This is great news and an awesome “extension” to an already very useful plugin!

I get the error:
before-after-block.js:1 Uncaught SyntaxError: Identifier ‘el’ has already been declared at before-after-block.js:1

And no block to insert in Gutenberg. I tried to change el in the scripts with elTwenty. To no avail. But I am not a programmer ??

Hey Mark, I will do.

Thank you.

It’s kinda complicated. On one website I disabled BackupBuddy and it connected flawlessly. On my own website I disabled BackupBuddy and I got the same error when trying to connect the Instagram account. Strange enough on my own website I now have the latest posts showing up.

On both websites the popup showing an Insta post is empty.

Here are both sites:
https://www.hoggen.ch/
my own: https://www.fullframestudios.ch/

I could give you a BackupBuddy license if you install a sandbox WordPress somewhere I can add my BackupBuddy license for you to investigate. I would dearly appreciate this getting resolved asap. Just let me know what I can do to help.

Thanks for looking at this.

I disabled Backupbuddy, tried to reconnect the account but it didn’t help.

Thanks for this input. I will communicate that.

No I don’t see /wp-admin.

It’s a nice plugin for translation, I even considered going pro. But I will talk to the Oxygen dev’s and see if there’s a less cumbersome solution to this.

Thanks for your reply. Sorry for my late reply, I was away a few days.

I am using Oxygen Builder as mentioned. And the translation drop down appears twice. Once for the entire browser window and then within the editable content.

GTranslate definitely messes up the editing. I always have to make sure that I enter text to the set base language set in the plugin. Else it will actually store translated text.

For instance:
– Base language set to Spanish
– Translation drop down set to English
– Open a page and edit it with the Oxygen Builder
– I enter text in Spanish and the text is translated to English and saved in English

Which results in the text not being translated once I look at it in the front end because the plugin detects English text, anticipating Spanish text.

Soo, long story short. I have to disable the plugin, make my edits and re-enable the plugin. This is cumbersome. Maybe you can reach out to Oxygen Builder, or make a demo install here and test it yourself: https://oxygenbuilder.com/try/

Thanks & Cheers

Thanks @edo888! That fixed it. It appeared not because of updating the plugin, but because I switched the settings of GTranslate to “Auto switch to browser language”.

It would be nice to have a setting where the plugin would not try to translate in the back-end.

Cheers & Sorry for my late reply,
Alex

Answering my own question.

Yes, it’s possible. I changed the sites language to Spanish, so everything is renderd in Spanish in the front-end, and then set the user language to English so my back-end is English.