snck

Hey @bernhard, I usually use a setup where a production website and a staging website are on the same file system. I love the filesOnDemand feature because it saves a lot of disk space for the local development system and also for the staging system, but it is also very slow on sites with a lot of assets. I think it would be great to be able to specify a local path instead of a URL to a website (or in addition). Ideally, if a local path is specified, then if a file or variation (for images) is not present, filesOnDemand would first search via the specified alternate path to see if the assets are present and deliver them (without downloading or copying) directly. The assets folder of the staging system would therefore only grow when a user creates new pages or makes changes to existing ones, but not when content that exists in the production system (on the same file system) is to be accessed. I assume that filesOnDemand has so far been developed primarily for downloading assets that are only available remotely. But perhaps it could also cover this application purpose - or a new feature with a different name? Cheers, Flo

Unfortunately this strange behavior reappeared. 😞 But at least I got some more errors in rockmigrations.txt: As the (growing) indentation indeed looked like a loop to me I had another look at the releases of RockMigrations. In this case commit 476963f (feat: add refresh() before installing new module) seems to be the culprit. Commenting the refresh() in line 2454 in RockMigrations.module.php does the trick for me: // if module is not installed do a refresh // this is necessary sometimes (don't know why) $unindent = false; if (!wire()->modules->isInstalled($name)) { $this->log("Install module $name"); $unindent = true; $this->indent(2); // $this->refresh(); } else $this->log("Already installed $name"); The logs indicate that there might be something going wrong with the installation of ProcessRockMigrations? After uncommenting the line above again, the error did not reoccur. I tried to reproduce it by re-running the Github Actions, but everything seems to be working so far. @bernhard, maybe you could have another look at the refreshs and/or the routine installing ProcessRockMigrations? This might be an edge case, but one that could be prevented?

Marked as solved. It might have been an issue of correctly updating RockMigrations. I completely removed the submodule, made a commit, added RockMigrations as a submodule again (main branch, 6.0.1), commited and pushed to Github and now everything is working as expected. At least this might be helpful for somebody running into similar issues.

Hello everyone, Unfortunately, I have been having problems with “endless loops” for several versions (>=5.2.0), which obviously always occur after the update when the migration routines run. I have now observed this on two different websites. The starting point and procedure was similar for both: Prerequisites: ProcessWire 3.0.229 Local development with DDEV Github repository with main and dev branch Integration of RockMigrations as Git submodules Automatic deployment via Github Actions and RockMigrations Procedure: Update the RockMigration version from <5.2.0 to a more recent one (5.5.0 or 6.0.1) Push the respective branch to Github, then automatic deployment via Github Actions Problem description: Deployment runs without error messages or similar. Website is accessible (until login attempt). On login attempt timeouts and various error messages (see below) Various entries in modules.txt (see below) Website can no longer be accessed (timeouts and exceptions) A downgrade to RockMigrations 5.0.1 has so far resulted in the pages working reliably again in all cases. errors.txt: 2024-11-27 16:11:25 ? https://production.example.com/processwire/ Schwerwiegender Fehler: Maximum execution time of 120 seconds exceeded (Zeile 255 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesConfigs.php) 2024-11-27 16:12:52 ? https://production.example.com/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 117 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesFiles.php) 2024-11-27 16:13:52 ? https://production.example.com/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 311 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesInfo.php) 2024-11-27 16:14:26 ? https://production.example.com/processwire/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 1660 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/WireFileTools.php) 2024-11-27 16:15:49 ? https://production.example.com/processwire/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 334 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/WireData.php) 2024-11-27 16:16:25 ? https://production.example.com/wir/impressum/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 191 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesFiles.php) 2024-11-27 16:16:59 ? https://production.example.com/fokus/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 191 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesFiles.php) 2024-11-27 16:19:39 ? https://production.example.com/processwire/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 255 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesConfigs.php) 2024-11-27 16:20:13 ? https://production.example.com/processwire/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 588 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesFiles.php) 2024-11-27 16:22:38 ? https://production.example.com/processwire/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 191 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesFiles.php) 2024-11-27 16:23:54 ? https://production.example.com/processwire/page/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 191 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesFiles.php) 2024-11-27 16:25:16 ? https://production.example.com/museum/ausstellungen/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 191 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesFiles.php) 2024-11-27 16:28:52 ? https://production.example.com/museum/ausstellungen/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 255 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesConfigs.php) 2024-11-27 16:29:26 ? https://production.example.com/processwire/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 471 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/modules/LanguageSupport/LanguageTranslator.php) 2024-11-27 16:31:11 admin https://production.example.com/processwire/page/ Schwerwiegender Fehler: Trait "RockMigrations\MagicPage" not found (Zeile 5 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/site/classes/ContactRolesPage.php) 2024-11-27 16:31:14 admin https://production.example.com/processwire/page/ Schwerwiegender Fehler: Trait "RockMigrations\MagicPage" not found (Zeile 5 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/site/classes/ContactRolesPage.php) 2024-11-27 16:31:23 admin https://production.example.com/newsletter/ Schwerwiegender Fehler: Trait "RockMigrations\MagicPage" not found (Zeile 5 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/site/classes/ContactRolePage.php) 2024-11-27 16:35:06 ? https://production.example.com/processwire/module/ Schwerwiegender Fehler: Maximum execution time of 120 seconds exceeded (Zeile 307 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/modules/LanguageSupport/LanguageTranslator.php) 2024-11-27 16:35:39 ? https://production.example.com/processwire/module/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 316 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesInfo.php) 2024-11-27 16:37:14 ? https://production.example.com/processwire/page/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 311 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesInfo.php) 2024-11-27 16:38:06 ? https://production.example.com/processwire/page/list/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 589 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesInfo.php) 2024-11-27 16:38:53 ? https://production.example.com/processwire/page/list/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 255 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesConfigs.php) 2024-11-27 16:39:26 ? https://production.example.com/processwire/page/list/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 311 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesInfo.php) 2024-11-27 16:43:21 ? https://production.example.com/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 255 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesConfigs.php) 2024-11-27 16:43:52 ? https://production.example.com/processwire/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 191 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesFiles.php) 2024-11-27 16:43:54 ? https://production.example.com/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 198 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/WireCacheDatabase.php) 2024-11-27 16:45:09 ? https://production.example.com/processwire/page/ Schwerwiegender Fehler: Maximum execution time of 30 seconds exceeded (Zeile 117 in /var/www/vhosts/example.com/production.example.com/release-20241127142315-a7d461c4/wire/core/ModulesFiles.php) modules.txt 2024-11-27 15:23:32 ? http://example.com/http404/ Found 1 module version changes (applied when each module is loaded): 5.0.1 => 6.0.1: RockMigrations 2024-11-27 15:23:32 ? http://example.com/http404/ Found 1 module version changes (applied when each module is loaded): 5.0.1 => 6.0.1: RockMigrations 2024-11-27 15:23:33 ? http://example.com/http404/ Found 1 module version changes (applied when each module is loaded): 5.0.1 => 6.0.1: RockMigrations 2024-11-27 15:23:33 ? http://example.com/http404/ Found 1 module version changes (applied when each module is loaded): 5.0.1 => 6.0.1: RockMigrations 2024-11-27 15:23:33 ? http://example.com/http404/ Found 1 module version changes (applied when each module is loaded): 5.0.1 => 6.0.1: RockMigrations 2024-11-27 15:23:33 ? http://example.com/http404/ Found 1 module version changes (applied when each module is loaded): 5.0.1 => 6.0.1: RockMigrations 2024-11-27 15:23:33 ? http://example.com/http404/ Found 1 module version changes (applied when each module is loaded): 5.0.1 => 6.0.1: RockMigrations 2024-11-27 15:23:33 ? http://example.com/http404/ Found 1 module version changes (applied when each module is loaded): 5.0.1 => 6.0.1: RockMigrations 2024-11-27 15:23:33 ? http://example.com/http404/ Found 1 module version changes (applied when each module is loaded): 5.0.1 => 6.0.1: RockMigrations 2024-11-27 15:23:33 ? http://example.com/http404/ Found 1 module version changes (applied when each module is loaded): 5.0.1 => 6.0.1: RockMigrations [ over 800 of these lines following ] Has anybody experienced a similar problems? Cheers, Flo

Hey @Mike Rockett, thanks for this module! ? I was wondering whether it's already possible to exclude certain languages, e.g. using a hook. I have a website that has a few languages installed, but one language is used only for internal stuff and the pages should not be accessed from the outside. What can I do to prevent MarkupSitemap from outputting links to page versions using one specific language completely (even if the language version is "active" on many pages)?

Thanks for the input, @ngrmm! After further investigation, it became apparent that the editor who was experiencing the problem always accessed the backend of the website via a bookmark that referred to a URL with a www subdomain. Since the www subdomain is not set up as a host in config.php, the "View" link always points to the domain without www. Presumably the session cookies were running on the subdomain, which were not classified as "same site" by the browser and/or cookie policy, which may have led to the 404 error. For me, this has now been resolved. I was at least able to solve the problem for the editor by using a rewrite rule that redirects all traffic for the www subdomain to the main domain. Since then, the strange behavior has no longer occurred.

I have a strange problem with a site that I was not able to solve until now. I have a website running on domain.com (which is also the only entry in the hosts array). If an editor (or me as superuser, but for me this is happening only sporadically) is logged in (also using domain.com/processwire/), they cannot access an unpublished page using the "view" link, but get a 404 error page. If the previewed url is changed from domain.com/xyz/page/ to www.domain.com/xyz/page/ manually in the address bar, the page is viewed correctly. There is no .htaccess rule for www redirects in place and I have disabled ProCache for debugging purposes. What makes it even more bizarre: Sometimes if the user logged out and is logging in again, they get redirected to the page they wanted to view directly after submitting the login form. Has somebody experienced a behaviour like this before? As I am not able to reliably reproduce this behaviour, I feel a little lost. At first I was thinking that this problem is related to some network configuration/filter/firewall stuff on the client's network, but as I was also facing it a few times, I am really confused. Is there any configuration on the webhost side that could cause issues like this? Any input is appreciated! Thanks, Flo

@Juergen After testing with a colleague we found some points that could probably be addressed: Translations: German translation shows "VERöFFENTLICHT" (instead of "VERÖFFENTLICHT"). Maybe it could just be "veröffentlicht" (no CAPS, but bold)? If you have set a publish date (in the past) and save a page as unpublished, you get a warning, that the page will be published on the next run of the cronjob (same for unpublish date...), which is fine. We were asking ourselves, whether the method that is triggered by the cronjob should also run on page save (for pages that have values in the module's fields). This way the warning could be changed to something like "you have set a publishing date in the past, the page can only be unpublished, if you clear the field...". We think that (although the message that is shown is clear about the effects) it is not the best possible experience that a change has an effect, but only for a short time and changes back automatically after that. Warnings might not be read everytime. Page tree: If a page is published (because of a publish date in the past) and gets unpublished directly in the page tree, the warning mentioned above is not shown (because it is an ajax request) and the user will not notice, that the page will be published again soon (only if he reloads the page tree manually). I do not know, what the most elegant solution is, but I think, hooking $pages->[un]publishReady() and "stopping" the (un)publish action if it is against the settings in the module fields (and outputting a warning that explains the reasons) would be a solution that also solves the problem mentioned above. As I said, the improvements are huge already. These are no necessary changes, but suggestions on how the module could become even better. ?

@Juergen Thank you! ? We are still testing it, but it's looking good! A massive improvement over the previous versions. ?

@bernhard You are completely right! ?‍♂️ We can consider that solved, I guess. Thank you!

Hey @Juergen, thank you! That was so quick that I am not sure whether I can test and implement it before you release the next version. ? Visually it looks great to me! ? But I think, the method should be "smart" and also check whether the module has "fired" yet or if it will in the future (which should not be to hard as it is just a date comparison). I think the big value in highlighting pages in the page tree is in reminding the user that there WILL be a change to this page. The user should not be bothered by pages that already have been (un)published by the module and there could be a lot of those. You could even include a tooltip that gives detailed information on the (un)publication of the page if the user hovers over the clock icon like "Will be (un)published on XX.XX.XXXX – XX:XX:XX". I really love how quick you implement feedback. Thank you again! ?

@Juergen No worries! I am looking forward to it and happy to test, when it's ready. ?

And I just had another idea ?: Pages that will be changed by the module in the future could also be marked in the page tree, e.g. prefixed with a "clock" icon.

Great news! ?You could even attach a hook on page save that triggers a warning if a published page is unpublished manually, but will be published by the module again in the future (could work analog for an unpublished page that is published manually, but will be unpublished because of a "publish_until" date in the future).

I would disagree on that. If you only want to schedule publication of some of your pages, you would not expect anything to appear in these fields on pages that have been published manually. In contrary I think it is misleading this way, because it looks like the publication had been scheduled, although it was not. I think it is much clearer if the fields give a clear indication of the user's intention: Blank = nothing happens Filled = publish/unpublish at this date/time Imho the page status is handled by PW and editors should be aware that they can publish and unpublish pages manually. Your module is a great addition, but in my eyes it should enhance the core functionality by offering a way to schedule publishing/unpublishing without forcing additional actions or altering page data. Maybe it would be a nice addition to show a status in the fields that informs the user about the effect of the module like that (in an InputfieldMarkup or as description of the fieldset): Page is currently PUBLISHED, no settings have been applied Page is currently UNPUBLISHED, will be published on XX.XX.XXXX – XX:XX:XX Page is currently PUBLISHED, will be unpublished on XX.XX.XXXX – XX:XX:XX You could even make it really fancy and include a countdown or something like that. This is of course just a quick thought and I do not want to "order" new features. I just wanted to address the user experience aspect and make a suggestion how it could be improved.