98dac9b314
This odd dependency is causing inclusion issues to do with namespacing and the ability to work well with the framework (according to the dependency's readme). The usage of the tool in this case adds no value, as it's performing purely stub type work, rather than mock work. So instead we can use an actual stub (simply return test values depending on input) and have everything work well. After removing the Phockito dependency it was found that the tests that would skip when it isn't present were actually in a failing state. So they had to be repaired too, mostly through the use of fixing the poor code that was causing them to fail (as opposed to being bad tests). This is both configuration and proceedural work. |
||
---|---|---|
.tx | ||
_config | ||
javascript | ||
lang | ||
src | ||
tests | ||
.editorconfig | ||
.gitattributes | ||
.scrutinizer.yml | ||
.travis.yml | ||
.upgrade.yml | ||
README.md | ||
changelog.md | ||
code-of-conduct.md | ||
codecov.yml | ||
composer.json | ||
license.md | ||
phpcs.xml.dist | ||
phpunit.xml.dist |
README.md
External links
Introduction
The external links module is a task and ModelAdmin to track and to report on broken external links.
Maintainer Contact
- Damian Mooyman (@tractorcow) damian@silverstripe.com
Requirements
- SilverStripe ^4.0
Note: For a SilverStripe 3.x compatible version, please use the 1.x release line.
Features
- Add external links to broken links reports
- Add a task to track external broken links
Installation
- If you have composer you can use
composer require silverstripe/externallinks:*
. Otherwise, download the module from GitHub and extract to the 'externallinks' folder. Place this directory in your sites root directory. This is the one with framework and cms in it. - Run in your browser -
/dev/build
to rebuild the database. - Run the following task http://path.to.silverstripe/dev/tasks/CheckExternalLinks to check for broken external links
Report
A new report is added called 'External Broken links report'. When viewing this report, a user may press the "Create new report" button which will trigger an ajax request to initiate a report run.
In this initial ajax request this module will do one of two things, depending on which modules are included:
- If the queuedjobs module is installed, a new queued job will be initiated. The queuedjobs module will then manage the progress of the task.
- If the queuedjobs module is absent, then the controller will fallback to running a buildtask in the background. This is less robust, as a failure or error during this process will abort the run.
In either case, the background task will loop over every page in the system, inspecting all external urls and
checking the status code returned by requesting each one. If a URL returns a response code that is considered
"broken" (defined as < 200 or > 302) then the ss-broken
css class will be assigned to that url, and
a line item will be added to the report. If a previously broken link has been corrected or fixed, then
this class is removed.
In the actual report generated the user can click on any broken link item to either view the link in their browser, or edit the containing page in the CMS.
While a report is running the current status of this report will be displayed on the report details page, along with the status. The user may leave this page and return to it later to view the ongoing status of this report.
Any subsequent report may not be generated until a prior report has completed.
Dev task
Run the following task http://path.to.silverstripe/dev/tasks/CheckExternalLinks to check your site for external broken links.
Queued job
If you have the queuedjobs module installed you can set the task to be run every so often.
Whitelisting codes
If you want to ignore or whitelist certain http codes this can be setup via IgnoreCodes in the config.yml
file in mysite/_config
CheckExternalLinks:
IgnoreCodes:
- 401
- 403
- 501