I recently want to commit a change to my WordPress plugin repo but it has been showing 'Access to '/!svn/me' forbidden' error whenever I wanted to commit any changes. Some articles have adviced me to check if my username and password are correct but it seems not to be the right solution because my login credentials are actually correct. Please, has anyone faced this issue before or is there an alternative to TortoiseSVN that I can use? Thank you!
I published a first small plugin on wordpress.org. I tried to follow all steps but the banner does not appear. I named my banner like this : banner-772×250.jpg I commit with svn on the assets folder on the root Notice : The icon is visible. what could be the problem ?
I am running WordPress on Ubuntu with Apache and MySQL. I would like to automatically install minor and security updates to WordPress. However, as I understand it, the standard auto-update mechanism (see also How exactly do automatic updates work?) is ultimately fired off by a web request, meaning that the update process runs as the apache user (for me it's www-data). So the www-data user has to have permissions to write to WordPress's php files. This makes me uncomfortable - …
I'm embarrassed to say that I am a bit clueless on the procedure used to update a plugin via tortoise svn even though my plugin has been on the repository for years and had over 300,000 downloads! there's a lot of questions about svn here but they've only confused me further :-z somehow I've managed so far but I need to know the proper procedure for updating my plugin to the new version with regards to committing the trunk and …
A lot of questions are about plugins and themes, that you don't necessarily have installed. Downloading zip archive, unpacking and opening in editor seems like a too much hassle. If only there was a way to just browse source of WordPress and all of plugins and themes in its repository...
Before I start: I'm not sure if this is feasible so any guidance, suggestions, criticisms are welcome. I'm looking for an easy way to deploy my Wordpress theme code from my development environment (local computer running WAMP) to my staging and production environments (both are hosted servers). The ideal workflow I am looking for would utilize Apache Subversion as my source code repo and would look like this: Make changes to my Wordpress theme in my local environment, Commit code …
I plan on submitting a Gutenberg block to the repo. What am I supposed to submit? Only the compiled code is distributed. Based on how the SVN repo works, it seams I should NOT be submitting the source code.
I've submitted a few patches for WordPress core on Trac (one of which has been used) but every time I think about doing it I cringe because my setup for doing so is incredibly tedious. Can someone please detail out the steps needed to submit a patch for core, and then the best way to streamline the process so it's not so tedious? I work Mac OS X and PhpStorm currently but I'm thinking a shell script might be easiest? …
We're trying to commit and push our initial release to the SVN repository assigned to us by the wordpress team. However when committing the code we're getting an error (probably because of the PHP8 polyfill) but are a bit baffled why this is stopping the plugin from being deployed? In the readme.txt and composer we specifically also set the min. version of PHP to 7.0
I can't understand why, but I can't rid of old (unnecessary) screenshots of my plugin in WP Directory. I've removed assets folder from each version in tags, removed assets folder from trunk, made commit, but on the plugin's page on WP Directory those images still here. If I hover cursor over some unnecessary image - I'll see hash of commit which firstly contain this image. How to get rid of this image?
I can get latest WP using latest.tar.gz http://wordpress.org/latest.tar.gz How to get latest plugins? I checked about svn i need to know when new version is out and in command svn sw put latest link so thats bad option. Trunk is bad couse its development so that means it can be not be stable therefore not called stable version. So for WP ill use link latest.tar.gz But what to do with plugins? They have one more problem. They dont have latest. …
I use Subversion with my websites. Up until now, this has meant creating a new repo for each of my sites. However, this is wholly inefficient as it means me lugging around the whole WordPress source for each of the sites. It also has meant that I have to copy plugins between repos and thus duplicate the code each time. So what I wanted to do was have a repo which only really contained my theme file (and possibly other …
If I am pushing a new version (v0.2) of my plugin (v0.1) on the repo, what does I do with the stable tag in readme file? Change it to v0.2? What should come here? Clarifications please :)
I develop my plugin over on github but when it comes to deployment I have to somehow copy my changes into the Wordpress SVN. Currently I do this manually and copy over each file in each directory individually, but this is time consuming and error prone. I have seen and tried a few scripts but I think I must be running them wrong as they either error or don't copy over the files correctly. So my question is has anyone …
I realize this may be a broad question on the surface, but I'm looking for specific examples of setups/workflows that people use to keep a version history of edited files on a WordPress site. For instance, when developing a site (and even after it's live), I often make changes to CSS and PHP files, but I don't have a great way of reverting to older versions of those files. For my purposes, making changes on a local development installation and …
I have a DEV environment setup with wordpress installed, where I have a wordpress developer working every day. I don't feel comfortable every time he changes something in the environment because there's no way of tracking the changes he's doing, so in the case there's an error o we want to go back 3 days for example there's no way for me to do that. I've thought about the different solutions to this problem and the only solution I have …
I tried to commit the changes to the “Filenames to latin” plugin and got the SVN error. The error message: Error: Commit failed (details follow): Error: Commit blocked by pre-commit hook (exit code 1) with output: Error: [Error output could not be translated from the native locale to UTF-8.] Error: This error was generated by a custom hook script on the Subversion server. Error: Please contact your server administrator for help with resolving this issue. The latest code for the …
I created a plugin using Gutenberg blocks. I have a node_module folder because its using dependencies like Wordpress components. The plugin folder size is about 100 Mo. I tried to use SVN to commit and push the files but it's very slow: About 3 hours to commit the files and the post commit never ends ... I waited 2 or 3 hours more, but it seems stuck. I used CLI and RapidSVN and the result is the same. Do you …
When committing my plugin to the repo, I'm getting an error that looks like this: Commit blocked by pre-commit hook (exit code 1) with output: *********************************** PHP error in: path/to/file.php: Parse error: syntax error, unexpected '?' in path/to/file.php on line 36 Errors parsing path/to/filephp Examining the line in question, I see that the ? is part of one of PHP 7.1's nullable return types: static function foo($bar=null): ?string { ... } Note that my readme.txt file correctly notes the minimum …