Fully recommend!
]]>I’ve made some updates to my plugin but cannot seam to get it to move to the next version. I have a bug and fixed it, but the changes don’t show up even though the repo seams to have every piece of code from the new version. I’ve set up version and stable version, even removed old tags just to make sure – but nothing seams to work. Any ideas that might help?
]]>Certain website hosts such as Pantheon enforce strict version control for the /wp-content/plugins/
folder, which means that we can’t save logs to this location.
If we could set the logging path to a location that doesn’t use version control, such as the uploads folder, that would solve the problem.
Thank you for considering this!
]]>I am building my first theme with the full site editor.
On the index page, I have several query blocks that show posts from specific categories. It seems that selecting queries hard-codes the category IDs into the theme template file.
We’re using GIT to handle version control and have dev, staging, and production sites. I’d very much prefer to not replicate the database across each for various reasons, and it isn’t easy to manually keep IDs in sync across them.
Specifically, in the “taxQuery” part:
<!-- wp:query {"queryId":14,"query":{"perPage":3,"pages":0,"offset":0,"postType":"post","order":"desc","orderBy":"date","author":"","search":"","exclude":[],"sticky":"exclude","inherit":false,"taxQuery":{"category":[13,12]}},"align":"wide","layout":{"inherit":true}} -->
Is there a way to use the category slug or some other method to not have hard-coded IDs in the index.html template file?
Thank you for your help.
]]>Is there any wordpress plugin which can be used to host&manage a “Software Repository System” and a “version control service (not client)”?
All i am looking for options to upload packages and have option to download it via git://, ssh://, Http(s)://
Also good to have if it offers package sharing options between multiple OS (like NFS, CIFS..etc)
Any help/pointers will be appreciated.
]]>Download Manager’s version control allows me to upload the new versions without changing the published download links, enabling users to download older versions if they need them, and control which downloads are available to the public and which are members-only.
Download Manager has proved completely reliable, and I have no hesitation in recommending it to other WordPress site owners.
]]>For example, if a pdf document with procedures should be available on multiple pages and the procedures are updated, the document must be replaced by a new version. I will then have to check all the pages with links to the document and manually update them.
Surely this could be easier, with a symbolic link plugin or something? What is the simplest solution to ensure that the same version of the document is available on all pages at once?
]]>Could you please help me? Or point me to a resource on the web to read.
Thanks
]]>I checked out WordPress’s plugin developer guidelines, and there doesn’t seem to be a rule against big surprise overhauls, but in this case it sure seems…uncool. It looks like the developer is somehow obliging people to upgrade and has switched from free support in the WP forums to paid support on their plugin site. A big problem there is, the new version doesn’t seem to have been tested very well for conflicts with other plugins. Some of the commenters in that thread said it made their site unusable.
Now, usually you’d just say “Uninstall it and choose a different plugin” or “revert to an earlier version”. But with 400k installs and a good % of those people using auto-update, you’re going to have a ton of issues that go unnoticed until a site visitor hopefully pings the site owner.
Typically a developer would make a separate, premium plugin rather than completely re-engineer their old one. Are there unstated ethics or applicable WordPress TOS that apply to this scenario?
]]>