JayGee

Are you 100% certain it is Cloudflare causing this issue. It took me many years of using ProcessWire to realise that it was me causing logouts by opening the browser dev tools device emulator for testing during site development. This happens because it sends a new user agent header and triggers a new session in the browser, therefore logging you out of the old session. You can see this happening in the PW logs - it records it as 'session invalidated' or similar.

Just an idea - not particularly thought through so may not work!... Because you can so easily add another URL to ProcessWire sites via the config, I wonder if you could use a separate URL or subdomain for editing access that doesn't go through CF. You could restrict access for editing by IP so other people can't use that domain.

We use various versions of this module on a lot of sites and I also haven't come across this. Do you have the actual error message?

Have you ever listened to the podcast Darknet Diaries - this is the exact vibe I always get about how these hackers are operating. Begrudging admiration for the ideas they come up with. Given that most email css is inlined, does this require the machine or platform of the mailbox doing the forwarding to be compromised? Otherwise how are they modifying the CSS without the forwarder's intervention? I guess a dodgy browser extension could also do this ? I.e. target the CSS of known mailboxes e.g. when you visit gmail or outlook. EDIT: After reading the article I realise I misunderstood the concept. So they're not modifying existing emails, they're sending and email with this method build in as hidden payload. I guess the lesson being to ensure trust of the original message.

Hi @ryan does this module handle frontend edits?

I think you may have made the same mistake I did in that original post... $collections->sync_queue("product={$product}, limit=1"); // this not work in hook should be: $collections->sync_queue->find("product={$product}, limit=1"); // this not work in hook (find missing in the top one).

@ryan - Have just implemented this in a production project to fill a very specific need and it has worked a treat. Thank you! ? ? ? ?

It was on latest stable 3.0.229. Updating to latest dev 3.0.231 seem to resolve it. For clarity I'm doing to work updating a fairly old site - so I can't 100% say it isn't something in the legacy code or a Handover from the older PW version I updated from.

12hrs later I can confirm everything is running smoothly so far! Will report back on this thread if any issues. But great to know we can use MarkupRegions retrospectively on older sites like this.

Are people still actively using Hanna Code? I'm trying to do an install of it on a site for the first time in a while. Hitting a problem getting the module to install. The text formatter will install, but not the Hanna Code module meaning I don't get the editor (even with the config added or site in debug ?).

Found answers here: https://github.com/processwire/processwire-issues/issues/1307 I think this happened to me today as I ran an update on an older install that hadn't been touched for a while rather than it being an issue with current PW.

Is there any update on this? Also seeing this error in 3.0.299 and it's causing some issues installing modules.

Just checking something I've not done before... I've upgraded an old site to PW latest stable and I want to add some new features using MarkupRegions but only on one template. I've enabled MarkupRegions in config as usual but skipped the append. I've then appended my _main.php file in the template settings instead, so as to target it only to one template type in the site. $config->useMarkupRegions = true; //$config->appendTemplateFile = '_main.php'; <--- added this manually to one template in the UI instead of via config.php Is this ok? It seems to be working, but just checking I'm not introducing any unforeseen pain? I've only ever used MarkupRegions as an all-of-nothing type thing before!

Yes this is what I was doing... but turns out I had a typo and it was loading my 404 page in the panel I think. This is why I was getting the nav bar showing ?. The panels now work exactly as expected (and as you describe) to load my module functionality! ?

Sorry to be clearer on my question - what I'm wondering is whether there's a core method for injecting dynamic content to PW panels and modals in the dashboard rather than writing new logic. I know you can load a page into the panels, however that then seems to reload the whole dashboard interface including nav etc inside the frame.

Hi all, I'm looking for some examples/guidance/tutorials on how to populate a PW panel from a module. I know you can open a UIKit panel with a .pw-panel css class and that you can populate it with a custom admin page. But I'm wondering the best approach to populating with dynamic module-specific content, e.g. a form? TIA J

I think some of the confusion arises around mixing terms for bootstrapping and multi-instance. Unless I'm mistaken, I've always taken multi-instance to mean a multi-site scenario. I.e. multiple sites running off one core or database (or various combinations of this). Whereas bootstrapping allows one codebase to interact (including page creation) with the API of 2 disparate ProcessWire installations without needing to create your own custom endpoints. But as @Robin S has highlighted above I'm pretty sure I've been able to write ok to bootstrapped PW instances, although it has been a while since I've done it so would need to test to be sure.

Cool - interesting insight thanks just to see what others are doing. You could also try the bootstrapping method which I think would allow you write between sites too through the regular PW API. https://processwire.com/docs/front-end/include/

Purely out of curiosity can I ask the nature of your project you need this for? We’ve done a few app projects where we’ve considered separation of concerns over multiple PW instances but have never ultimately thought it would be beneficial versus just running 1 site.

I completely missed your thread on this when searching this issue - some helpful stuff there thanks.

Ahhhh thank you - penny drops, aha moment! ? This works - the template-specific classes need to extend DefaultPage and not Page... painfully obvious with hindsight that it should follow usual inheritance rules. I'm not 100% sure it's clear from the docs though, I think I was expecting some kind of PW magic to kick in and inject the DefaultPage methods. Either way I know now and this awesome PW feature becomes even more useful. Thanks all. ? Edit: I now also realise this is exactly what @Charming Troll's reply was demonstrating. - thanks.

Hi all, sorry for the delay I was away for a few days and thanks for the responses so far. So the contents of the class file (DefaultPage.php) are as follows: class DefaultPage extends Page { public function test() { return 'test'; } } My understanding (maybe wrongly) is that in this scenario $page->test() should then be callable in any template? However I get a method is not callable in this context error. Yes this is enabled. Testing this in a fresh download of latest production PW where is enabled by default. (Other template specific classes and methods work too - e.g. /classes/HomePage.php). Other background info is that I'm using markup regions - I don't know if that could make any difference? Thanks, J

Have been loving working with the custom page classes feature since it was added, but haven't yet figured out if there's meant to be a built in way to add a class in /site/classes that will add methods for every template rather than for a single template type. I thought initially you could add a function to /site/classes/DefaultPage.php and call it as $page->yourCustomMethod() within any template but this doesn't seem to work - is it meant to?

Hey - I know how you feel, work is busy here too! I think you're right about the readme, I will update thank you. ?

Hey @Cybermano ? ... remember me! ? Sorry had a crazy few weeks at work and then a holiday, but finally got around to reviewing your great contributions on this module. I tested it and everything looks great. I merged your changes and also combined our readme files and added a thanks note/credit for you too ? Thanks again - you've taken this module way beyond where I originally planned. Only comment is I noticed when you first install it, the module will error on the front end because no languages are selected. I guess this is obvious when you think about it, but wonder if we should make that a compulsory field or pre-populate with at least one language? Thanks J (Finally changed my name on here too lol)