adrian

Hi @Sanyaissues - sorry you are having problems. I can replicate the problem with the custom template not working in PW 3.0, but aren't seeing the issue with the custom protected message not working - make sure you are editing the message on the Settings tab of the protected page. Now back to the custom template problem - do you have debug mode turned on in your config.php file? Do you then see this error: Notice: Undefined variable: loginForm in /pathto/site/templates/login.php on line 4 The problem seems to be passing variables using wireRenderFile. It works fine in PW 2.x, but looks like there might be a problem in PW 3.x Can you please confirm that this is the error you are getting. I am not really at my computer again fully for another a couple of weeks, but I will try to help figure this out. Anyone else out there reading this that has seen any problems with passing variables using wireRenderFile in PW 3.x?

Could you also add the new notes to the PageTable Automatic Page Name Format section on the Input tab?

Hey kixe, Thank you - this is awesome and solves one of my biggest issues with PageTable fields - getting meaningful page names without the possibility of conflicting names which I don't think the user should ever have to consider. One minor thing (but critical) - when installing with PW 3.x I get this error: Catchable fatal error: Argument 1 passed to ProcessWire\Pages::__construct() must be an instance of ProcessWire\ProcessWire, none given, called in /wire/core/Modules.php on line 481 and defined in /wire/core/Pages.php on line 128 It is easily fixed by adding an empty construct method to your module, like this: public function __construct() { // intentionally empty } I am definitely looking forward to using this with all my PageTable fields!

@FrancisChung - I am going to be offline for about a month, but please let me know how Migrator works out for you. I use it a lot in my development process for migrating new branches of content from dev to live, but I do know that there are still some issues that need to be sorted out. As I mentioned in the Migrator support thread, it's definitely not abandoned, I just need to find a good chunk of time to address some bugs. I would definitely recommend testing the migration from one dev site to another dev site first and if that goes as expected it should be safe to migrate to a live site. Also be sure to use the the inbuilt backup option just in case. Hopefully sometime in the new year this module will get some more love.

I have made the image editable as well though, so the problem is that the clicking on the top half edits the image, but on the bottom half edits the text, so not something that is acceptable - too confusing for the user. I understand the technical limitations though so not a criticism - more of an observation of a limitation.

Hey Soma, I still install this module on every site and was thinking that a nice addition would be to convert the "send_templates" pipe separated list of IDs to a comma separated list of template labels/names. Anyway, just a thought for when you're bored

I don't think that option is relevant for modes B, C & D, because they require you to manually specify the page that the field is on or they just don't work. eg, <edit field="image" page="<?php echo $other_page->id; ?>"> I am not sure about the performance issue - will wait to hear what Ryan says.

Speaking from experience, can I suggest running away very fast from JQM - check out Ionic instead

Try HookEvent instead of hookEvent

@Tom - that setting will appear once you check one of the fields. Ryan - the one thing I am noticing is that there is no way to choose B,C, or D. Nevermind I see that you don't need to choose the other options! But, I am also wondering what you think can be done about this: Notice the area of the paragraph - that translates into the area that is triggerable for edit mode by double-clicking - so the user mouses over the bottom half of the image and it looks like they can double-click on that and edit the image, but they can't - it just makes the paragraph editable.

Here is a discussion about the problem and link to the commit that fixed it in Oct: https://github.com/ryancramerdesign/ProcessWire/issues/1451

Still no problem here on 2.7.2 (the latest stable version) and 3.0.2. Is there any reason you are still on 2.6.1? Not saying that is the problem - I don't remember any changes that might have affected this, but might be worth a shot, and you have nothing to lose - there are so many great new features in 2.7.2. If you don't already use it, check out the Upgrades module as a simple way to update: https://github.com/ryancramerdesign/ProcessWireUpgrade

I have seen several drupal sites where the link in the html is still the /node/nnnn - does that mean they don't have it configured correctly or is this just something that is unavoidable in some cases, in which case that seems worse from an SEO point of view to me than just redirecting outdated links with PagePathHistory keeping in mind that there won't likely be that many changes - seems better than redirecting every /node/ link if it isn't being rewritten properly before the HTML is generated. However, a textformatter to rewrite ID links made by this module wouldn't be hard to put together - in fact I bet you could steal some code from the Link Abstractor module - which btw is now deprecated. If go to tackle this and need some help, please let us know and we'll help you get it working.

No problem doing that here. What version of PW are you running?

It seems to work just fine, but isn't officially supported, so your mileage my vary depending on your setup.

This sounds like a bug / oversight - perhaps you should file a Github issue about this.

Hi @gmclelland - to be honest I don't really use this module for replacement of the main links - I only use it as a means of providing a shorter URL if required. I actually think that the Page Path History module does an excellent job of preventing broken links. I have never actually been a fan of Drupal's /node/nnnn/ links, but in previous custom systems I have built, I have included the page ID as part of the URL, like: mydomain.com/nnnn-title-of-my-page/ which this module allows. As for changing the insert link - this should already work - at least it does for me: Sorry if I am missing your point - in a bit of a hurry! PS Did you select the "Rewrite Links" in the module settings?

What about this setting in Advanced Mode: Modules can accomplish almost anything - if you are willing to make a start, I am sure you will get plenty of help if you need it. There might be something useful in this thread: https://processwire.com/talk/topic/3543-register-users-and-add-page-same-as-username/ You might also like to look at the way the EmailNewUser module triggers an email when a new user is created - you might be able to use that as a starting point for modifying to create the member page instead.

Thanks for the report @ukyo - sorry that you and Ryan spent time debugging this. I have committed a new version which appears to fix the problem for me. Could you please test and let me know if it now works for you? If anyone is interested in what the problem was, take a read of the Github issue.

You wouldn't need another full module, you could just use AdminRrestrictBranch and add an additional hook that is triggered when a new user is added which takes care of creating the member pages. But, what I would do is use the "Multiple templates or parents for users" ability instead: https://processwire.com/blog/posts/processwire-core-updates-2.5.14/#multiple-templates-or-parents-for-users That way the member page is the user page, so one less thing to create and maintain. Sorry my answers aren't complete with examples today - lots to do and not much time

Could you put the X, Y, etc branches under an extra parent and just add that to the branch edit exclusions - that will take care of making all new ones excluded. I would suggest that AdminRestrictBranch might still be useful for you - you just need to add an additional hook somewhere that will automatically create the required branch when the user is created - this should be very easy - let us know if you need help. You might also consider connection the user to the parent branch by one of the other options - role name or PHP custom code - this might be able to automate this process for you. Good luck with whatever approach you choose!

I guess my question for you, is does it work as you want? Seriously though, I think it should, but if the editors need to directly edit pages under Section X then you would need to use the "Editing Only" option, so that the page tree view is not actually restricted. With that setting, I think it should work as you described - how did it work out? Was there anything that didn't work as you need?

I think I must be missing something - have you tried the AdminRestrictBranch module? Can you please highlight exactly what it doesn't support for your needs - perhaps they might be a worthwhile addition, or perhaps not

@clsource - fantastic writeup - thanks for sharing!

PageTableExtended can be used for generating previews: http://modules.processwire.com/modules/fieldtype-page-table-extended/