Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The author of this plugin is not available. #476

Open
VaLeXaR opened this issue Jan 16, 2017 · 30 comments
Open

The author of this plugin is not available. #476

VaLeXaR opened this issue Jan 16, 2017 · 30 comments

Comments

@VaLeXaR
Copy link

VaLeXaR commented Jan 16, 2017

He is not answering on private message or email.
Can anybody create fork and will include all fixes for future users?
It is bad when only one developer has access to the development of this plugin.

@The3IC
Copy link

The3IC commented Jan 18, 2017

Also the support pages are down so seems this is the end of the line?

@TheDubliner
Copy link

Are you volunteering VaLeXaR? 😉

@VaLeXaR
Copy link
Author

VaLeXaR commented Jan 19, 2017

@TheDubliner I'm ready. But needs somebody else. Need a team that did not happen, as with this project. Are You ready?

@TheDubliner
Copy link

@VaLeXaR I guess the answer for the radio silence here can be found in this thread.

@VaLeXaR
Copy link
Author

VaLeXaR commented Jan 19, 2017

@TheDubliner at last the author of this plugin appeared.

@raykai
Copy link

raykai commented Jan 20, 2017

i got a post from the Plugin Author John Clause today saying:
"I am sorry for your trouble. We currently do not have resources to answer support questions for free"
"We need to figure out a way to monetize the support and further development."

you can see the full post in the attachment or at this link:
https://wordpress.org/support/topic/bug-with-wp-4-7-sub-page-in-breadcrumb-bug/#post-8676360

its dead

@adeacetis
Copy link

adeacetis commented Jan 21, 2017

John isn't taking care of the plugin since July '16. When I asked in the forum what happened to him, I received a vague answer from forum-s administrator. Since then, I was busy with other stuff and, I have to admit, disappointed with how things were going on here. So, I didn't follow up.

I totally understand he could be busy at making a living but that is not fair for the community. Many solutions here:

  • We fork the project, create a new community with a new dynamic with more than one administrator ;
  • John gives admin access to a couple of other devs that would handle the pull request and answer at issues;
  • All of us switch to another plugin and make it successful.

Two first solutions are my favourites. I'm ready to contribute actively and be part of a team that would make qtranslate-x more user-friendly so he would compete with WPML.

I suggest we open a Slack channel and start the team. Should I take care of this ? @raykai @VaLeXaR ?

@VaLeXaR
Copy link
Author

VaLeXaR commented Jan 21, 2017

@adeacetis if @johnclause agree, I am not against. Of course, to develop the project alone is difficult. But for a sufficient number of volunteers and a few trusted administrators can develop this project. Contribution to the project @johnclause very large. Today qTranslate able to compete on equal terms with WMPL.
But if @johnclause wants to monetize this project, the community can make a fork and develop a free version.
A good example WP Sync DB, which is a fork WP Migrate DB. This project has 1378 stars and very popular, with great functionality.
P.S. Sorry for my english :)

@adeacetis
Copy link

adeacetis commented Jan 21, 2017

Hi agree, @johnclause has made a HUGE contribution to the open source community. I'm not against he wanting to monetize his work but we need a more dynamic development cycle. We should be able to improve the plugin in a much faster fashion.

Good you've mentionen WP Sync DB, this is an awesome WP plugin.

Are we going to wait for @johnclause 's feedback ? What's the next step ?

@johnclause
Copy link
Member

johnclause commented Jan 21, 2017

I agree we need more dynamic cycle. I appreciate your compassion and understanding. I hope to gather a little bit of money after enough people do the recently published survey, and then we will be able to put a license server together. Meanwhile, we also need to take care of a few hot issues already reported after the latest WP updates. Hopefully within the next couple of weeks.

@VaLeXaR
Copy link
Author

VaLeXaR commented Jan 21, 2017

@johnclause, I think, WPGlobus is a fork of original qTranslate. This is seems like this. It have a free version and paid version. Logic of work is similar. And WPGlobus becoming popular.
Everyone is waiting for your decision on further action.
Competitors do not sleep. :)

@adeacetis
Copy link

adeacetis commented Jan 21, 2017

I didn't know about WPGlobus. It has indeed a lot of positive reviews. I'll answer to @johnclause survey Tomorrow. I'll get back to you afterwards.

@johnclause Can you help us out by labeling the hot issues you mentioned ? If not done yet, I'll put a list of the issues together and will post it here.
Once we know what should be done I suggest we review the hot issues related to new WP versions and split the load among us.

Cheers,

This was referenced May 7, 2017
@blw
Copy link

blw commented May 17, 2017

Any update on this? Can @johnclause add a few more admin to the repo maybe that will help?

@herrvigg
Copy link

herrvigg commented Aug 30, 2017

hello,
any news about this? Several months have passed now and there is no sign of life. This is an excellent plugin but it's really sad it doesn't get any update.
If the main author (ownership?) wants to setup a paid support why not, and it could make sense for some business users, but it shouldn't prevent regular updates. Is there only 1 person having control over this?

WP Globus is much more active and i tried it. It's pretty good. Yet i wouldn't switch because qTranslate-X offers more functionalities (more options such as the difference between languages order and default language). But at a certain point if the main author doesn't move anymore, either the community should fork the project or move to another one. Preferably, the current qTranslate-X should continue to live, as it would benefit from the knowledge of the people here.

@VaLeXaR
Copy link
Author

VaLeXaR commented Aug 30, 2017

@herrvigg while I`m waiting for the author's reactions, I developed my own plugin
https://wordpress.org/plugins/wp-multilang/

@amouratoglou
Copy link

Hi @VaLeXaR does it work right out of the box with sites using Q-translate-x and addon plugins of Q-translate-X ?

@VaLeXaR
Copy link
Author

VaLeXaR commented Sep 7, 2017

Hi @amouratoglou . My plugin is not compatible with addons for qTranslate. This is distinct plugin. I just use syntax of qTranslate for separate language string.

@amouratoglou
Copy link

So I guess that we can say RIP qtranslate-x ?
I will have to consider switching to a new translation tool...
this happened one time before when qtranslate was abandoned...
then qtranslate-x appeared...

@Blackbam
Copy link

Blackbam commented Sep 9, 2017

Maybe somebody will show up and have the time to develop it further. Just speaking for me I do not need all the fuck WPML and the other translation Plugins offer.

  • I want to handle translation within a single post or page with a single ID
  • I want to choose easily which Custom fields are translated and which not (most are not such as prices, numbers, ...)
  • The only odd thing is the title and the editor, duplicating those I have always done with the qTranslate switcher
  • I do not care if RawML or duplication is used for multilanguage fields

If nobody will show up and develops qTranslate further as soon as I have the time I will create a simple as fuck language Plugin in the style of qTranslate for the translation of post types, taxonomies and option pages - or maybe I try to develop it further. However like most people I do not get paid for GPL software and I am still hoping someone else will do it ;-)

@amouratoglou
Copy link

amouratoglou commented Sep 9, 2017 via email

@Blackbam
Copy link

Blackbam commented Sep 14, 2017

@amouratoglou Sure but I had a few looks into the qTranslate code and it is possible - but a lot of work to make it ready for the future. Is there any information about further development?

What you say is true: As soon as full incompatibility with a new WordPress version arisis tens - maybe hundreds of thousands of websites will be down and even worse, they probably can not be repaired easily.

@amouratoglou
Copy link

amouratoglou commented Sep 15, 2017 via email

@VaLeXaR
Copy link
Author

VaLeXaR commented Sep 15, 2017

@amouratoglou qTranslate-X have error when using REST-API. It is also difficult for integration with other plugins. That's why I created my own plugin for multilingual. My plugin is compatible with those sites that use qTranslate-X or WPGlobus.

@openmtbmap
Copy link

I think the whole editor should be kicked out - it's just replicating functionality and often gets broken. you can get much easier using [:] [:XX) tags. Make it simple, use the syntax and try to have it working in as many places as possible. That's all what is needed.
Well I would like to have a syntax that is like [:XX|YY] so meaning content after this is only in language XX and YY but not other languages. [:] all languages and [:XX] single language. Of course that will make an editor much more complicated as the editor would need to filter a lot to find what is has to show - but as said no need for editor.

@Blackbam1337
Copy link

@amouratoglou Somebody MUST update it or it will start breaking slowly. Furthermore there would be still some optimizations which should be implemented (Permalinks, Widgets, Menus, REST-API, ...).

@openmtbmap In my projects I always have to provide a layer above this syntax as it is considered "to be to complex for customers to use it". This is sad but true.

Anyway you can always easily split the content and make seperate fields, the only really fucked up thing to duplicate in Widgets etc. is wp_editor. But even this problem should be solvable.

@The3IC
Copy link

The3IC commented Sep 15, 2017

@VaLeXaR great initiative! A couple of comments/questions:

  • Are you planning on making this a paid extension/add a paid version? I would warmly suggest that so that the same thing does not happen to your plugin that happened to qTranslate-X.
  • I would be very happy to switch but I have also used the qTranslate slug to translate the all site slugs, cannot switch now without destroying my SEO it seems? Any plans on integrating aTranslate slug-like functionality? The slug extension can be found here: https://github.com/not-only-code/qtranslate-slug
  • one of the problems I have faced with qTranslate has been with meta (for FB/og, Twitter etc), do you support translated meta information?

@VaLeXaR
Copy link
Author

VaLeXaR commented Sep 15, 2017

@The3IC

  • Not now. I think this is must be free plugin. In other CMS multilingual is from box.
  • For this, I need to write a new functional. I do not need it yet. Maybe later. But not now.
  • What plugin do you use for displaying a meta for social networking?

@The3IC
Copy link

The3IC commented Sep 16, 2017

The plugins that I have tested are "Facebook Open Graph, Google+ and Twitter Card Tags" and "WPSSO". Currently using the meta features of AllIn1 SEO which kind of works but the overall meta support in AllIn1 is rather poor so I would really like to use a better/more dedicated plugin.

@The3IC
Copy link

The3IC commented Sep 16, 2017

@VaLeXaR ps: in case you want to keep the basic plugin free, perhaps some add-on functions like the slug etc could be then a paid-for module to secure some revenue for you?

@tivnet
Copy link

tivnet commented Sep 18, 2017

Just to clarify: WPGlobus mentioned in one of the previous comments is not a fork of the original qTtranslate. It was indeed inspired by the qT plugin and we wrote it when the original qT was abandoned. However, the codebase is completely different.

We have never followed the development of any qT forks and do not officially provide any compatibility with them. If however, someone wants to switch from a qT site to WPGlobus and discovers any specific issues, we'll be glad to help to fix them.

Thank you!
Gregory
TIV.NET INC. / WPGlobus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests