* https://plugins.svn.www.ads-software.com/starbox/tags/
At the time of writing, it looks like your most recent release was v3.4.3, released 2 months ago. But your most recently-tagged release is v3.1.9, released 3 years ago.
* https://plugins.svn.www.ads-software.com/starbox/tags/3.1.9/
Please make sure to tag your releases so that admins who install your code via svn are able to pin (and upgrade) to a specific versions.
Thank you
]]>https://plugins.svn.www.ads-software.com/recent-posts-widget-with-thumbnails/tags/
]]>Still version 1.2, would expect it to be at least 1.3 and ideally 1.4.
]]>If I check out trunk, it looks like the docroot is the src subdirectory. So the instructions seem to want me to put wp-config.php in the root of the checked-out working directory. It seems like that ruins the point of the exercise, to not pollute the working copy with site-specific files. Is there an updated version of these instructions? Should I be checking out the src directory and not getting all the tools? That seems to violate the spirit of the repo reorganization.
]]>I’d like an additional option to ONLY disable html minification without disabling the entire plugin.
ie. I’d like an option to keep js and css minification, comment removal and relative urls and ONLY disable HTML minification.
That way I can view my HTML properly formatted.
So the top two options would be:
Disable plugin: [x]Enable [ ]Disable
(Enable or disable plugin)
Minify HTML: [x]Yes [ ]No
(This option typically set to ‘Yes’)
I have first fresh version of plugin approved by WordPress. Then i got the subversion repository in my email however i made a mistake to upload my plugin in the repository.Mistakenly i have uploaded my whole folder into the trunk folder then i came to know only subfolder and the files should have to placed in the trunk folder.I don’t know now my plugin is in what state it’s been two week but it’s still not showing my profile’s plugin directory.can anyone help me with this? you can track my activity by below link.
Thanks in advance.
]]>Additional background: Initially, the upload was somehow interrupted or left incomplete. Also, I uploaded an “assets” folder within the main trunk rather than according to the “new” method in which assets get their own folder. I just a few minutes ago deleted the unneeded assets folder left within the trunk folder (for a while the same images were located within both assets folders).
NO CONFIRMATION/CHANGE EMAILS: For whatever reason I never received a confirmation email, either after the initial incomplete upload, nor after adding missing files. Nor have I received a confirmation/change email upon a subsequent upgrade, though I have received one for a different plugin also updated around the same time.
“Plugin Not Found”/”Plugin file does not exist” ERROR ON UPGRADE: The repository is accepting changes and is numbering them, and upgrade notices do appear where earlier versions of the plug-in have been installed, BUT activation after the upgrade fails with a “plug-in file does not exist” validation error. After clicking “activate,” the plug-in works fine.
I do not know if these two problems are interrelated. EIther way, I am at this point at a loss as far as either of them goes.
]]>