@distantnative It works well, a couple of quick observations
When clicking the + on the fails row it wasnât clear I had switched to the redirects screen. I clicked again and it asked if I wanted to delete, I thought this was the fails, not the redirect.
I canât seem to be able to set up a home redirect.
putting in / doesnât redirect at all, shows the home content which is default, but title shows âerrorâ and fails count goes up
leaving it blank results in a white screen with no content.
Edit: I was able to redirect home with a 301, not 200 which I had before. 200 appears to work redirecting anywhere but home.
No 1: I get it and will try to find ways to make this clearer.
No 2: I have to check all the details of it. Part of it is that 200 is not a redirect code, only those in the 3xx range are. So it wonât redirect but either deliver a page instead at the current path with the code or fail with the code. Though I need to check whatâs happening with the title and the track count. Also never thought about a redirect of / as I thought, youâd rather set the Kirby home option.
You mean it is wrongly flagging requests as failures or itâs correctly flagging failures but you are surprised where these failing requests are coming from?
Seems it keeps failing on some of the normal content, but really not sure why or whatever, everything shows ok on the pages, and the referrer being the homepage ⊠I donât want to blame the plugin until I know for sure its not my site (its complex)
Or maybe the plugin isnât to blame here: Look what the console displays on your home page. There really seem to be a lod of media files that cannot be loaded and produce fails:
Today I actually understood what you mean and fixed it: In the next beta you can put / in the âRedirect toâ field and it will be resolved with the home page. The thing with the status codes is still: Everything in the 3xx range will actually be redirected, other codes will lead to the page being returned but under the same old URL with this particular status code. Iâd say for the vast majority of cases, you should go for a 3xx code.
New beta will handle this better: Clicking the + on the fails row takes you to the redirects screen with the form opened and the path prefilled. If you click add on the bottom right, the new redirect is added. If you click cancel, it gets discarded.
Yes, but with the normal images. Since I cannot find the @2x image paths in the source code with a quick cmd+F, I assume those request arise from one of your JS plugins/scripts.
Once more a lot of refactoring since beta 3. This time to tackle all the issues around multilang and/or custom template components. let me emphasise how much I appreiate everyone testing it â I hope we are getting to a stable 1.0.0 in the near future.
Require Kirby 3.0.3
Added permission handling
Added tbl-for-kirby for tables
Implement new workflow for adding fails as redirect
Refactored big parts of code base
Simplified interface parts
Fixed redirecting to home /
Fixed smaller display issues
Improved documentation
Update from beta.3
Due to issues with plugin loading in multi-language sites and/or with custom template components, we moved away from storing redriects in the content/site.txt. Instead we store them now in site/config/redirects.yml. Learn more in the release notes.
Will be happy to get some more tester before the final release.
Fixing a crucial issue encountered with older Vue versions. If you encountered the error Cannot create property 'column-status' on boolean 'true' this new release is for you.
Hi @distantnative, Iâve just tried to install the plugin via download/unzip and as soon as it is autoloaded, I get HTTP ERROR 500 for both my local site as well as the panel.
Iâm using MAMP 5.2 on MacOS High Sierra with the .htaccess from the starterkit for RewriteBase /myprojectname and the other Kirby-related RewriteRules.
Your plugin looks amazing, but Iâm a bit stumped as to what I can do to make it run.
I just checked and it works for me with a fresh starterkit in a subdirectory and RewriteBase just fine. So probably something else. Are you using any other plugins? What PHP version are you on?
I am using PHP 7.2.14. Iâve tested a few more things:
I disabled the only other plugin Iâm using (kirby-builder): no effect
I upgraded to MAMP 5.3 so I could switch from PHP 7.2.14 to 7.3.1: Iâm getting a Exception originating in /Applications/MAMP/htdocs/myproject/kirby/vendor/filp/whoops/src/Whoops/Util/TemplateHelper.php with preg_replace(): JIT compilation failed: no more memory. Apparently this is a PHP 7.3 related Bug which I have not yet been able to circumvent with the published workaround (set pcre.jit=0 in php.ini). Perhaps itâs not as easy to fix in MAMP.
I installed Retour in a fresh checkout of the starterkit with my PHP 7.2.14 setup: it works.
I installed kirby-builder on top of the Retour-Starterkit-Testcase: it still works.
I copied over the /kirby directory from the current version of the starterkit into my project: Retour is suddenly working.
Apparently I had an older Kirby core that wasnât compatible
This really needs more testing in real-life situations like yours to figure out reliable ways to track those fails.
or
or
I assume itâs caused by the RewriteBase. I hope Iâll be able to check this tomorrow evening.