Your website (wpastra.com) says that you store all your code on GitHub, but I searched the list of repos in the org linked-to in your website footer, but I couldn’t find anything named ‘astra-sites’
Please link to the primary forge where users can browse the code, submit PRs, bug reports, and feature requests for the ‘astra-sites’ plugin.
]]>Looking forward to continue to use this plugin in the future.
]]>In this case we commit all our plugin files to our repo, and deploy them with a CI tool, but the .gitignore file included ignores the vendor directory resulting in a critical error.
]]>I recently encountered an issue while installing the simple-page-ordering
plugin via Git. I noticed that the 10up-lib/wp-compat-validation-tool
directory contains an embedded .git
repository. This leads to a problem when the plugin is installed in a project that is also under version control with Git. It essentially adds another Git repository inside the existing one.
Having an embedded .git
folder is generally not advisable unless it’s intended to be a Git submodule, which does not appear to be the case here. It creates complications for users who clone the repository or install the plugin as part of their version-controlled project.
Could you please remove the .git
folder from the 10up-lib/wp-compat-validation-tool
directory to prevent this issue?
Thank you for your attention to this matter.
Best regards,
Tudor
It would be great if they are able to add more content types, for example, I’d love to be able to display code samples from Github Python py files.
]]>In an attempt to test this I built our master branch back to staging and the site worked again, so then I logged in, and went to plugins/deactivated the Visualizer plugin. Then I built the update branch back to staging and the site works still. All good so far. I login to the site, navigate to plugins and attempt to activate the Visualizer plugin, but am greeted with the following error output.
Warning: require(/var/www/html/hub/wp-content/plugins/visualizer/vendor/composer/../markbaker/matrix/classes/src/Functions/adjoint.php): Failed to open stream: No such file or directory in /var/www/html/hub/wp-content/plugins/visualizer/vendor/composer/autoload_real.php on line 41
Fatal error: Uncaught Error: Failed opening required '/var/www/html/hub/wp-content/plugins/visualizer/vendor/composer/../markbaker/matrix/classes/src/Functions/adjoint.php' (include_path='.:/usr/local/lib/php') in /var/www/html/hub/wp-content/plugins/visualizer/vendor/composer/autoload_real.php:41
Stack trace:
#0 /var/www/html/hub/wp-content/plugins/visualizer/vendor/composer/autoload_real.php(45): {closure}('3af723442581d6c...', '/var/www/html/h...')
#1 /var/www/html/hub/wp-content/plugins/visualizer/vendor/autoload.php(25): ComposerAutoloaderInit0cfa41381204c801cf9e0304c5326c72::getLoader()
#2 /var/www/html/hub/wp-content/plugins/visualizer/index.php(136): include_once('/var/www/html/h...')
#3 /var/www/html/hub/wp-content/plugins/visualizer/index.php(175): visualizer_launch()
#4 /var/www/html/hub/wp-admin/includes/plugin.php(2314): include_once('/var/www/html/h...')
#5 /var/www/html/hub/wp-admin/plugins.php(192): plugin_sandbox_scrape('visualizer/inde...')
#6 {main}
thrown in /var/www/html/hub/wp-content/plugins/visualizer/vendor/composer/autoload_real.php on line 41
And just to confirm this is strictly related to building an updated plugin, I re-deployed master to our staging environment and manually clicked the update button in the plugins page for Visualizer, and it updated just fine, without any errors. The main issue here, is that we use a bitbucket repo to make sure that our developers all have the same plugins available to them.
Hoping you can help!
]]>https://prnt.sc/Q2gNp3Fvh3NY
https://prnt.sc/VWpSYuYfkXW-
]]>