-
Notifications
You must be signed in to change notification settings - Fork 110
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
WordPress Repository Status #222
Comments
Comment by michael-milette I am looking for the plugin as well. |
Comment by Gersnij Me too! I installled the plugin on one site, and need it once more.. |
Comment by MarcoNko I was looking for the plugin repository too, panic! |
Comment by ianchanning Everything seems to have gone very quiet on this. Given that qtranslate-x is the recommended replacement for mqtranslate which is fully deprecated as of WordPress 4.3 this becomes more urgent |
Comment by adamlindqvist I'm also looking for the plugin! Hope to see it back soon. |
Comment by ianchanning N.B. Anyone can download the master branch and upload the zip file to get the plugin back. You'll also need to unzip qtranslate-x-master.zip, rename it to qtranslate-x and rezip it if you want to make sure the plugin gets updated properly when it is reaccepted into the WordPress plugins directory. |
Comment by Grafcom @mrwweb @michael-milette @Gersnij @MarcoNko @adamlindqvist and @ianchanning We are currently investigating this, please have patience. |
Comment by Gersnij I'glad @mrwweb has commented today that there is hope we will have this plugin back. Thank you. |
Comment by ianchanning @Gersnij i think it's pretty risk free. Any reason for the plugin being taken down was because of a bug in the very old qtranslate plugin - but it doesn't exist in the qTranslate-X plugin. As long as you rename the downloaded directory and re-zip it before uploading it to your site via 'Plugins > Add New' then the plugin will work normally and then you'll get prompted to update the plugin once it's added back into the WordPress plugins directory. @Grafcom let me know if I can help at all |
Comment by Grafcom @ianchanning |
Comment by Gersnij Are you sure it should work that way? I followed the instructions (download the master from the link, unzip, rename the folder and underlying folder to qtranslate-x, zip again, add new plugin via upload), but it says - in Dutch: unzipping, installing, package cannot being installed. No valid plugins found. |
Comment by mrwweb I'm happy to install it via GitHub for now. I'm just looking for an |
Comment by mvandemar For those who didn't notice the above activity, it appears to have been pulled due to a valid vulnerability, which @ianchanning is working on fixing here: |
Comment by richpav Until development restarts here, is @ianchanning 's fork the best to to use? |
Comment by ianchanning I'm confident what I submitted should work and addressed the security concern that WordPress raised. I tested as best I could the fix I made, but I could have introduced a bug as this is my first time modifying the plugin.
|
Comment by Grafcom @ianchanning |
Comment by mvandemar @Grafcom Have you resubmitted the plugin with @ianchanning's fix to Wordpress yet? |
Comment by johnclause Sorry for the delay with security fix required by WP. The fix is now submitted and plugin should be back after WP approves it. I am closing it for now, we can still write into a closed issue and may re-open it again if needed. |
Comment by johnclause |
Comment by michael-milette It's back on WordPress.org! See https://wordpress.org/plugins/qtranslate-x/ Have a great weekend!
|
Comment by Gersnij Congrats. Nice job! |
Issue by mrwweb
Saturday Aug 22, 2015 at 18:14 GMT
Originally opened as qTranslate-Team/qtranslate-x#222
I see in the 3.4.3 changelog that the plugin was temporarily pulled from the WordPress.org repository (and still is as of August 22, 2015). Can someone give a status update on whether the security concerns are valid, whether they've been fixed, and if/when we can expect the plugin back in the repository?
The text was updated successfully, but these errors were encountered: