Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author adispiac

    (@adispiac)

    Hi,
    Sorry you feel this way, however giving the plugin a failing grade should normally be reserved for plugins with weak support, unresolved bugs, security issues, or not following WordPress standards. Which is certainly not the case for TranslatePress.

    To put things in perspective, without our paying customers the free version (which is used successfully on ~ 70K websites) wouldn’t even exist.

    Expecting a WordPress plugin to be unconditionally FREE even when used for a potential revenue creating website, is just hurting the WordPress ecosystem (which you are also part of).

    Good luck with your project and hope you find a suitable solution,
    Adrian

    @rerique your review don’t seem to be fair – sorry. And as the plugin is 100% GNU GPL you can use it on as many sites as you like, you can copy and modify it too so that it fits your needs to integrate more than one language and when you even publish your development on a public git account I am sure many woudl even join to help to improve and fix some really major flaws.

    The usability of that plugin is really the best you can get but unfortunately you might loose ll your translations which have been done by automatic translation when you end i.e. yor google subscription – as meanwhile Google Translation like their Google Map usage can eat up your Google credits pretty fast and then you have no translation – well the translation gets stored in the database but somehow there seems to be a major problem to connect those translations from the internal translation memory again to the records and all that record connecting stuff causes on bigger sites a huge speed issue.

    It is so sad that the translations do not get stored together with the record itself like it should be done if done professionally. Check out how TYPO3 is doing it. or check out Processwire how they store all the records. Something like that (i.e. the Processwire way) would completely avoid that speed issue and the loss of translations as the translations would be in the same record as the record itself.

    This said – Until now I don’t rate that plugin but I would give it a ZERO for security of your translations and 5 for the usability as that is the best in class with only a minor problem. It would be great to have a button right the way beside field to translate which would enable you to translate automatically the content with a translation service i.e. google, bing and there are many more. I hope you will have a look to Processwire and try to implement their way in storing records as that would finally end up then for sure in THE number 1 plugin with a 5 for data security and storage and a 5 with usability. But until then I can only recommend to avoid that plugin and instead use a free alternative i.e.https://github.com/VaLeXaR/wp-multilang which seems to have lots of parallels with your plugin.

    @adispiac

    Expecting a WordPress plugin to be unconditionally FREE even when used for a potential revenue creating website, is just hurting the WordPress ecosystem (which you are also part of).

    You are part of that ECO System too and a FREE plugin can create much more REVENUE for great developers (which you hopefully are) than any other commercial plugin (mostly commercialized by NON Developers with no or limited coding experience) – this is how the ECO system you describe looks like. The GNU GPL ECO system is INSPIRE TO SHARE!!!

    What would be the benefits of making your plugin in full publicly available?
    1. Immediately many more people would use and switch to that plugin
    2. Many more BUGS would get discovered
    3. Many more people would help to fix all those bugs
    4. Many more useful features would get integrated, more translation services, perhaps even an open source translation memory integration ??
    5. The storage problem would get solved immediately as people would rely on the 100% functionality as all other alternatives with great Usability would be pretty expensive to use.
    6. Ethically you are reselling Open Source Code NOT programmed and written by you too so don’t blame others by doing the same with your code if they do to improve the data flaws and making a FREE translation plugin available for all here in WordPress
    7. YOU as the developers would get a 5 star reputation as the ones who brought a FREE 100% translation plugin to WordPress with Great usability + WooCommerce and SEO compatibility + automatic translations. This reputation woudl bring you tons of projects which you can work on (well but as mentioned above – that would probably only work if your team is not a mostly “marketer team relying on other developers” but rather a developer team itself. You would get invited to talks, conferences as one of the really inspiring people of WP who bring back the original GNU GPL sense of “Inspire to share” back to WordPress leaving that commercial ECO system far behind. All other translation plugin developers would need to revise their ECO system policies too if you go 100% public with your repositories and encouraging a community approach or perhaps eve an official integration to WordPress Core (check out how Babel was storing their records in WordPress – unfortunately that project seems to be dead) YOU could revive that!!!

    @renrique Fork the plugin and give it a try to build up a community version if they are not doing it!

    @toremo awesome reply. Agree with everything you said!

    Also hope your suggestions about the automatic translations, their storage and manual triggering of automatic translations per string are implemented.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Just a crap’ is closed to new replies.