HerTha

see my post here:

The Site Indexer module has been in use on one of our websites for quite a while. It worked very well for us for extracting text from PDFs. I just started to review the site in order to make it work with PHP 8.1. It turned out that some adjustments would be necessary at a few places, including the Indexer module. My PHP skills are quite limited, but the module author @Alessio Dal Bianco was so kind to give me a helping hand (thanks Alessio!). The additions of @DaveP's fork have also been incorporated. The result can be accessed on Github (v0.8.3 branch): https://github.com/USSliberty/Processwire-site-indexer/tree/v0.8.3 Happy Wireing!

Thanks @FireWire for taking the time and providing the hint! This PHP version madness creates me a decent amount of headache. Anyway, meanwhile I was lucky to get some additional help from the original module author @ussliberty - the updated code will be available here soon!

Hi @DaveP thank you for providing this module fork! It has been very helpful for many years on one of my sites. Could you imagine to work on this again, to get rid of a few PHP 8 incompatibilities? Some function parameters used for trim() and preg_replace() functions seem to require a modification. My PHP skills turned out to be too limited when I tried to patch this myself...

okay, got it - it's embedded in a check already: if( ... function_exists('get_magic_quotes_gpc') ... great that there are source files to look into 🙂

Shouldn't be there when it comes to PHP8, right?

I guess I found the trick: Duplicator offers a setting "Flush ZIP after quantity of MBytes" Tried setting "500" and voila, the backup finished successfully on that all-inkl server. Happy New Year!

The process stops after 40 something seconds, don't think there is a limit already.

Thanks for the hint! There is a recommendation not to exceed 5GB when running a PHP backup script: https://all-inkl.com/wichtig/anleitungen/datensicherung/webspace/php-skript-zum-sichern-der-ftp-daten/einrichten_97.html If that is valid, 2GB should not be a problem. Will check with all-inkl support to get this confirmed...

Comrades: Copied a site to a new server at all-inkl All went very well so far, but when I start a backup using Duplicator, the script terminates after a minute or so. The backup zip actually starts being written (with FTP, I can see how the file size increases) but stops at about 1GB (and file disappears). The server is running PHP 8.1 and I have a .user.ini file in place to establish higher PHP limits already, like: max_execution_time = 600 memory_limit = 1024M Checked that it came into effect using phpinfo(). Anyone having a clue, what other limits could prevent the backup file from growing larger?

Hi Pip, for me, it is not clear what you mean here - basically, using a Page Reference field sounds like a good approach for such an assignment of (a number of) 'ingredient' pages to an 'item' page. I think we need some more details to analyze the problem...

Thanks for looking into this! "link" is a VerifiedURL (pro) field, actually. In a template context echo $item->link just outputs the URL like any other text field.

Great to hear it works! Thanks for providing a summary to help others! This reminds me to #1 support rule:

This matches numerical IDs only, right? Could that be the reason for not working with text like 'agb'?

Installed the module and works out-of-the-box. Thank you very much for providing it! In my application I use a custom URL field named "link". So I replaced "url" with "link" in the module settings, i.e. in "Returned fields" and "Result template" and "Link template". Now, the url/link part is not inserted correctly, this is the resulting source: <a data-pageid="10666" href="[object Object]">@abcde</a></p> Could you look into this, if time permits? TIA!