Question: Status of development

[AntoninD]

Hi,

I have been following the start of the plugin originally on the qtranslate support forum. Since I don't see recent updates here, I wanted to ask what is the status of the plugin.

• Is it compatible 3.9.1 and will it be kept up to date in the near future?
• Will it be released on the wordpress plugin repository?
  If the outlook is rather uncertain, what would you recommend? Sticking with qtranslate (if so, modifications needed to keep it compatible?) or choose sth else?

Thank you and if development is in progress, good luck!

[nikolov-tmw]

Hi,

Currently the project is on pause – I’ve had a lot of stuff happen in both my personal and professional life, which left me with no free time to work on my plugin. I was really hoping to fully release it for WordPress 3.9, but that didn’t happen 😦

Unfortunately I have no idea when things are going to settle-in and I’ll be able to re-schedule my time to allow me to work on the plugin.

Right now the plugin is generally working( I’m using it on my site - http://themoonwatch.com/en/ ), but it definitely has some quirks and issues here and there that will not allow me to publish it for everyone to install.

If you can get qTranslate to work with the latest version of WordPress, then I guess you can keep using that. Unfortunately I'm not sure what else you can switch to, besides WPML(although as far as I know, that's also a far from perfect alternative)...

I hope that answers all of your questions, let me know if there's something else.

Nikola

[AntoninD]

Thank you Nikola.
I said it earlier on other plateforms but thank you for your work.
I didn't know your website; I would have seen a similar question asked few days ago by someone else.

• Would it be possible to know what is still buggy and/or not ready yet? So that if we consider that these features are minor or even useless to me and others, we could start using the plugin with the parts that work.
• If we were to use the plugin, could we at least be confident that it will be updated to be compatible with the coming core updates of Wordpress?

I have in mind simple websites who would need your plugin but they are already live so I just need to feel a bit confident about the basic functions.

Again, thank you and good luck. Your work is very much appreciated!

ps: can I consider that GitHub is the place to come to have status update on the project? Thanks for keeping us updated, even if it's to say that it's still on hold ;-)

[nikolov-tmw]

Hi Again,

Would it be possible to know what is still buggy and/or not ready yet...
Well - I really, honestly don't have any clue 😦 .
I know that every now and then, you might have a trouble saving a post(or page) - as in, you'd Publish it and then you'd get no content. From the feedback I've gotten on this, I know that if you hit your borwser's back button, you're fine. I haven't experienced it on my blog though.
Also, know that this plugin is also used on a couple of other sites, for instance: (a big one, probably not kept up-to date though) - http://www.sisecam.com.tr/en/ , http://www.x-pyr.com/en/ , http://zelenasofia.com/ . These are all of the sites I know of(and remember at the moment) - I don't get support requests from them often, so I'm guessing that things are going well for them 😃 .

Whenever anyone come to me with a specific bug they've stumbled upon(well, except the one where the post doesn't save), I always try to figure it out and fix it in the shortest time possible. Of course sometimes that's not possible(when I'm out of town, at a camp with no power, let alone internet access 😄 ), but I will eventually answer to an email, or an issue posted here(I get an email when new issues are posted).
On top of that, my idea when building the plugin was to use WordPress functionality as much as possible, in order to give it the best future-proofing possible(since WordPress is very good with backwards-compatibility). So in general, you shouldn't have any major issues with the plugin, even with new releases of WordPress.

What I always suggest to people that consider switching to my plugin is for them to set-up a separate, temporary clone of the site(you can set it up on your own computer, or on a sub-domain/sub-directory of the same domain) and install my plugin there. That gives you the opportunity to test-drive the plugin, see if you like the interface, whether it's compatible with your theme/plugins, etc. I can give you directions if you're not sure how to do that.

Yes - just follow the commits here. Keep in mind, that I usually push commits to the dev branch more often than I do to the master branch(that's because code on master is intended to be the latest stable version available).

Let me know if there's anything else I can help you with,
Nikola

[AntoninD]

Thx for the quick reply.
The owner of the website who asked me may not be tech-savvy enough to bother with contacting you if he has an issue to fix. So I'll find another quick fix for him. However, I am definitely looking forward to the progress (and ultimately the release) of the plugin so that we get a stable alternative to what qtranslate was.
Thank you again and good luck. I wish I could help you, maybe testing rather than coding, considering the level ;-)

[nikolov-tmw]

I see.

I really hope I'll be able to spend time working on the plugin...

Testing is always welcome, since I definitely can't test even a tiny
fraction of the combinations out there ;)

On Fri, May 23, 2014 at 1:38 PM, AntoninD [email protected] wrote:

Thx for the quick reply.
The owner of the website who asked me may not be tech-savvy enough to
bother with contacting you if he has an issue to fix. So I'll find another
quick fix for him. However, I am definitely looking forward to the progress
(and ultimately the release) of the plugin so that we get a stable
alternative to what qtranslate was.
Thank you again and good luck. I wish I could help you, maybe testing
rather than coding, considering the level ;-)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/45#issuecomment-43993773
.