WordPress plugin not showing the latest version after SVN commit - wordpress

Just yesterday i tried committing multiple versions just like i used to before in my plugin. I kept the new tags in tags folder as well however, the changes does not seem to be reflecting.
I already upgraded to version 1.4.6 but the repo is still showing 1.4.3.
First i thought this might be due to latest bugs in the repo however, its still not showing after 2 days.
Anyone know whats going on or what i am doing wrong ? Thanx
Note: The plugin is updated in svn repo in trunk and tags folder. The changes only are not being reflected in the WP Repo.
Check: https://plugins.svn.wordpress.org/inactive-logout/
Link to the plugin: https://wordpress.org/plugins/inactive-logout/

You're using the wrong Stable Tag version on your Readme.txt file. It should be your plugin version (1.4.6), not WP's (4.7).
See the documentation for “Tag” a new version": https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/

I have the same issue last week. Seems it's some kind of delay. I have recommitted by last weekend and my WordPress plugin page was updated this morning.

Related

New version of WordPress plugin not reflected

I'm new to WordPress. I was trying to upload a new version of my plugin after a bug fix. In trunk/readme.txt, I've mentioned Stable tag: 1.0.1. Also added all the new code to folder tags/1.0.1.
But still, when I visit my plugin's home screen, it shows the version as 1.0.0. Also, in side a WordPress admin page of a site, it says that latest version(1.0.0) of my plugin is installed which is not true. It should be 1.0.1.
Plugin : https://wordpress.org/plugins/negotiabl-woocommerce-extension/
SVN : http://plugins.svn.wordpress.org/negotiabl-woocommerce-extension/
What am I missing out? Please help me crack this
In addition to changing the readme.txt file and tagging, you also need to change the version number in the header of the plugin's main file - plugin.php file in your case.

update drupal to latest version causing weird themes issues

I have updated my drupal into latest version which is 8.1.9, i have succeded the updates, everything is seems fine except the Uninstalled theme section under appearance menu
it seems lots of unknown Uninstalled themes there which are not before, please refer screenshot
These themes might be introduced as part of core in new version i.e 8.1.9. Please check in themes directory for the same.
These test themes should not appear in your UI. When creating your original site, did you use the default.settings.php or the example.settings.php as source for your settings.php?
Please check, if there is a flag activated in your settings:
$settings['extension_discovery_scan_tests'] = TRUE;
If that's present, change it to FALSE and all the test themes should disappear.
See https://www.drupal.org/node/2759227 for a similar issue on d.o.

Wordpress plugin suggest not working properly

I am a WordPress developer and recently i created a magazine theme. In my theme, I used some (wordpress.org) plugins for my customer giving extra benefits. And after theme installation, my theme auto-suggest the plugins to install & for this, I have used tgm plugin (http://tgmpluginactivation.com/) for auto theme suggest.
i integrated that in my theme & it shows suggestion message on the dashboard for install that plugins. but the main problem is when I going to Appearance >> Install plugins. Plugins name shows perfectly and also its successfully install those plugins but under plugins name >> Show install button and also show a big link.
as we know, there will have only install button then clients will click on install button and install the themes. I tried many times for solve this problem. I am using the latest version of tgm plugin. & also I tried to solve this problem with old versions & its shows same result. For your kind information here's the Screenshot of this issue.
Kindly Help.
Yahoo .. i Solved this ,, actually i find out in that website, it was a bug but when i downloaded that plugin from github its finally solved automatically, that's mean plugin author updated and fixed the bug in github. i share this for newcomers, if anyone faced this problem, just download latest version from github (https://github.com/TGMPA/TGM-Plugin-Activation)
Screenshot for solve the issue
Thanks.

Upgrading Redux framework on wordpress?

I'm new to Wordpress, and in my plugin page I see Redux asking for upgrade.
A new build of Redux is now available!
Your version: 3.3.0.1
New version: 3.3.7.8
Get it now | Dismiss.
However unlike other plugins, it doesn't have any easy places to upload a zip or something. By clicking "Get it now", it simply takes me to its Github, where a bunch of code base exist, but again no instruction on how it can be quickly updated to the latest. Any hints? Thanks.
Sigh Lead dev of Redux here. Looks like the developer of your theme/plugin shipped with dev_mode on. That's not good. Let's get you setup.
I just created a plugin to disable this. Go here and install the zip as a plugin (and activate it): https://github.com/ReduxFramework/redux-disable-devmode (This will be on the WordPress Plugins Directory soon).
Then go to the WordPress repo and install the newest Redux Framework: http://wordpress.org/plugins/redux-framework/
That will get you all you need! Best of luck.

Ajax Error!!! parsererror in Wordpress

I have a local install of WP running on MAMP.
It is the latest 3.8.
I have installed a theme called Dante which is a pro theme and recommends various plugins (some of which are essential).
One of the plugins in called Revolution slider, and this is giving me grief.
I can install the plugin fine, however when I try and create new slider (from within the plugin) I get a message saying Ajax Error!!! parsererror
I have contacted the plugin supplier who have asked me to check the permissions of the plugin folder - I did (even made them 777) but no joy.
Can anyone help me as to where I should start debugging?
Many thanks
The problem lay with there not being enough memory allocated.
Adding
define('WP_MEMORY_LIMIT', '240M');
to wp-config fixed it.

Resources