Gabriel Gil

Hello again,

Thank you for your reply.

Apparently the error I was having disappeared after updating to version 2.0.5 you mentioned.

G.

Apologies, you’re completely right. I wrote this in a rush and it does not make much sense.

I am trying to explain that with the last update of this plugin, the functionality of another plugin I have installed stopped working fine. The plugins I am referring to is Product Extras for WooCommerce which allows me to add some extras to a product (I.e. Add a personalized message to a product, at a cost.).

The last update makes the cost of the extras to be discarded (So the grand total is only the cost of the product but not the extras).

Just great. Now trying! ??

I’m looking for doing exactly the same right now. Did you find any solution finally?

Thank you!

Could you share that plugin with us? ??

What a bad support service…!

The built in Customizer in WordPress since 3.9:

https://codex.www.ads-software.com/Theme_Customization_API

Wow. I love to hear all those ideas!

I think that I can do it, hopefully for the next major release. but i still having to check how could I use the API and manage to get all this points.

However, I’m going to add this issue to the GitHub repo, and take it into consideration while developing but if you’re not afraid, feel you free to create a for and start coding this feature on it ??

Thank you.

I think I’m not understanding you idea, but I would love to hear from you again but being a little bit more precise.

Thanks for your suggestions.

Hello!

Thanks for get in touch!

I like so much your plugin and i’m gonna take it in mind for future versions but, at the moment, i just wanna support public issue reporting and focus on new features like issue listing on admin area or frontend widgets.

However, you can fork it on GitHub and make a pull request if you really wanna see your plugin supported.

Thanks so much for your time.

Ok, cool.

So WPFE works as expected to me right now (Just waiting WP fixes the HTTPS core issue).

Thanks again!

About the Twitter issue, yes. It is a core bug.

About the Twenty Fourteen theme compatibility, yes. It works now using wpFE 0.7.3 but the featured image looks a little bit weird (Not at the original width). Check it out: https://snag.gy/cUdf5.jpg

Thank you!

Nope. I just get the content of the lang i’m actually reading.

For example (for a post saved from the backend and with both langs filled up.).

Given the post “my-post” y have 2 urls:

1. https://mysite.com/my-post
2. https://mysite.com/es/my-post

If i hit edit on the front from the https://mysite.com/en/my-post, i get just the spanish content, BUT if i then modify text and save, the english content is erased.

I think this is because qtranslate process the post content before it’s is returned to the front, and it saves BOTH langs if it is modified from the end. On the other hand, WPFE saves the post content as it is in the current lang (replacing this way, the other ones).
Note the different editing urls from the front creating the same result.

1. https://mysite.com/my-post/edit
2. https://mysite.com/es/my-post/edit

Sorry if i’m not explaining this good enough.

Regards.

Nope. It is a fresh WP installation and just using the WPFE plugin.

(I’ll be updated for the twitter fix)

Thanks.

Of course. You have to provide every lang translation.

Basicly, QTranslate wraps each translate like this tags. <!–:es–>Content<!–:–>

The content saved on the DB by qtranslate in two langs (spanish and english) will look like this:

<!--:es-->Content wrote by me in spanish<!--:-->
<!--:en-->Content wrote by me in english<!--:-->

The user never see this, because the plugin add a tab for each lang on the edit screen (Like the “Visual” and “Text” ones).

If in edit with WPFE a post, it replaces all the post content without the mentioned lang tags.

I noticed that it is on development, but i like and for that reason i’m trying help to make it better. ??