@HolgerAusB: in the footer there is an "About" link on my instance which gets you to that information
@jurgenhaas:matrix.org ahhhh. Its kinda hidden. In the German version I didn't notice that these are two links in the footer. I thought "wallabag - über" was only one link. So I allwys clicked on the first word and never found the about-page on the second one. Thank you.
Hi. Is there a way that a search engine could be plugged into Wallabag to replace the default MySQL search bar?
@virtadpt wallabag uses doctrine orm so adding a new engine implies to be supported by doctrine
The other thing to note is that the search bar is pretty 'stupid' right now, it does not even use mysql or postgresql fulltext functionality
The engine operates outside of the context of Wallabag. I suppose a better way to ask my question would be, how difficult would it be (for someone who knows nothing about PHP) to edit the theme or write a plugin for Wallabag that removes the existing search bar, and replaces it with a search bar that sends a query to a REST rail on localhost port whatever and turn the JSON that comes back into Wallabag search results.
I guess I should make my question more specific: is there an import method that under normal circumstances causes many articles (tens, hundreds) to have the same creation date? Occasional duplicates or unusual import data (which explicitly specifies the same creation date for multiple article) are not my concern
I maintain my own docker image of wallabag with a system to easily inject patches, I'm working to push it as a possible new official image. With this it could only imply to copy a patch to a folder to add this kind of feature
Regarding the Cloudflare cpatcha issue I wonder if it's worth talking to them and asking for an "agreement" so that wallabag sends a specific header which allows Cloudflare's border gate to identify it as such and avoid the captcha check. I've had a similar situation with drupal.org and they responded real quick. OK, much smaller scale, but as Cloudflare is known as the "good people" helping the net, they may well be open to that.
Hi, we (yunohost users) have a migration issue from 2.3.8 to 2.4.2 with mysql : wallabag/wallabag#5233. How can I help fix it? In a similar issue the fix was to alter the migration script (wallabag/wallabag#4832). I don't know why this is needed or if that's the best way? Maybe ping kdecherf since you provided the fix for the similar issue?