October: Flag and/or remove plugins from marketplace where their github repo has been deleted

[ayumi-cloud]

I would like to suggest the idea of adding some automatic quality control checks in the marketplace!

For example, if a user deletes all their github plugin repo's this would be a strong indicator that the plugins are no longer maintained and carry a risk of many bugs and errors!

It would be useful to users to warn them and/or prevent them from downloading such plugins.

Here are a few examples:

Marketplace link: https://octobercms.com/plugin/linkonoid-shortcodesengine
Github repo: https://github.com/linkonoid/shortcodesengine

Marketplace link: https://octobercms.com/plugin/linkonoid-scpincludecontent
Github repo: https://github.com/linkonoid/scpincludecontent

etc.

Clearly, it would be a waste of time for people to download and use any of these plugins.

It would be helpful if the marketplace did some automatic checks and flagged any github plugin pages that get deleted.

Create a cron job and check using the github api or git command if the repo exists or not once a day. If fails then flag or remove the plugin in the marketplace.

[bennothommo]

@ayumi-cloud FWIW, the repos above were renamed to https://github.com/linkonoid/octobercms-shortcodesengine and https://github.com/linkonoid/octobercms-scpincludecontent. The Shortcode Plugin was last updated on Sep 25, 2019 as well, which leads me to believe that they are using a manual method of pushing updates to the marketplace.

This would be evidence as to why we can't simply assume that a plugin is abandoned simply because their public repository link is out of date.

If you believe a marketplace plugin is abandoned, and you've tried contacting the author through the marketplace and had no response, then you always have the recourse of emailing [email protected] and getting the team to look into it.

[ayumi-cloud]

@bennothommo

Yah it seems you are right, about the renamed repos.

Though I still believe October should add an automatic check to make sure the repo's are not moved, renamed or deleted. If the automatic cron job github api check brings up a 404 then the code can send an email to the author, letting them know of this issue and if no reply from the author happens in a month period then an email should signal to the website managers etc.

Very simple to setup and automatics the process, making the website more efficient and less work for the managers to keep track of things.

That's my reason for keeping this issue still open.

[LukeTowers]

@ayumi-cloud automation follows process, so if this becomes a big enough issue that dealing with it manually becomes too cumbersome, I'm sure we'll develop automation to handle it. In the meantime, feel free to report this sort of thing to [email protected].

[ayumi-cloud]

Maybe one of the girls in the office can code a bot to scrape the october website and check all the plugins, then will email a mass list of issues.

[edit] ok sally is running a crawl through the website, you may see a spike in traffic today.

[ayumi-cloud]

If you are a plugin or theme author, please can you check out this list of errors and correct them if they belong to you!

https://htmlpreview.github.io/?https://github.com/ayumi-cloud/oc-marketplaces-issues/blob/master/October%20Plugins%20and%20Themes%20Issues.html

Let's keep the marketplace clean and high quality.

That is a list of broken links and assets to all plugins and themes in the marketplace.

p.s. Full list of october website issues will be discussed in private.

[36864]

That list includes obvious example links used in documentation (including example.com and localhost links) as well as links posted in reviews by users.

I suggest ignoring common test domains and ignoring the reviews tab when looking for dead links.

[ayumi-cloud]

@36864 Or the authors could write the code properly and use the correct HTML5 tags. Instead of creating a link, they should wrap them in a <code> or <mark> tag, e.g.

<a href="http://localhost/project">http://localhost/project</a>

should be

<code>http://localhost/project</code>

Or in markdown:

http://localhost/project

should be

http://localhost/project

---

As for the review tab - I have ignored them and you will not see any /plugins/support/ url's in that list.

[github-actions[bot]]

This issue will be closed and archived in 3 days, as there has been no activity in the last 30 days.

• If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue. - If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

[github-actions[bot]]

This issue will be closed and archived in 3 days, as there has been no activity in the last 30 days.
If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue.
If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

[github-actions[bot]]

This issue will be closed and archived in 3 days, as there has been no activity in the last 30 days.
If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue.
If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.