alan

Welcome Ryan and thanks for pushing the already tidied code back so quickly.

Yes true I certainly don't need to do that, I'd just assumed the best way to let my editors edit their sites was to give them a link on the site itself. But of course I don't need to (stupid me) I can just give them alone the URL by email. Thanks Soma for pointing out to me Thanks arjen and SiNNuT for the points and info, good to know that as usual PW has great sense and care and so uses these search engine bot rejections in the head. I will get rid of the login link

Has anyone implemented a simple method of hiding the login to PW from Google bot and the average person clicking about a site? I want to allow clients to login but I assume from a security POV it's better to not have a link to, say, /processwire/ in the footer as doing so publishes to anyone what is underneath. I know I can (and do) change the URL from /processwire/ to /something-else/ which helps, but I just wondered if anyone had implemented something better or if in almost all cases this [change of URL] is probably perfectly adequate?

@Ryan, I just noticed that if in config.php I have $config->debug = true; then whenever I submit a change to the settings of the LoginNotifier I see at the top of the rendered page: Notice: Undefined variable: this in /my-test-website.alan/site/site/modules/LoginNotifier/LoginNotifier.module on line 197 I assume this is nothing to be worried about and just a variable that has not been established before it's used (like I know what I am typing there... I know so little PHP ) Anyway I just thought I should let you know in case it's important.

Just found this module by accident (I must read through the list), excellent, thanks Ryan and Co.!

Thanks Pete and contributors for this excellent module!

Same here: I moved a site to a safe live hosting env' and had this error. The fix proved to be making /site/assets/ 777 and recursively applying that to all inside /site/assets/, that fixed it thanks posters.

@geniestreiche thanks for the link, that looks interesting and as if it might be an easy add-on to PW, albeit would mean edits to /wire (I assume) which I would not do, but if it IS easy to add this plugin and suddenly gain that additional functionality then maybe @Ryan/devs could be interested? @Nico I wish I were clever enough to write one Can a module add functionality such as the jQ plugin @geniestreiche mentioned? If so I'd like to look at that one day if I can ever get into module writing. @SiNNuT Yes it's for fear of losing work. Thanks I wasn't aware there were browser extensions. And I agree that swelling the PW core is something that is likely not a good idea for anyone. Though I wasn't thinking of revisioning (which I assume is significantyl more complex) just something that, say, when full screen (and so no visible Save button) if my browser crashes I won't loose all, only some, of what I typed since my last save. @Ryan/devs could the Save button be made visible when in full screen TinyMCE mode perhaps?

Totally understand and it's a huge ask to have the fiendish background-save-as-you-type sort of facility that Google docs has given all else PW is—can't (and shouldn't try to) be all things to all people.

You're welcome Nikola PS: Adding in my cal to check back here once in a while so I don't miss the release of this theme!

I do too:

This is a big ask probably, but when writing a large chunk of copy, particularly in full screen mode (assuming you're using TinyMCE or equiv facility) every so often I click save and have the inevitable page reload or if in full screen I drop out and save then go back. If PW were able to save in background when I click Save (so no page refresh) or auto save as per Google docs then that would be a major step for content editors. I am guessing this is mighty complex and so I'm not holding my breath and also this is not a 'big' issue, just one that I know would be a real step up for heavy editors.

Gorgeous! Thanks a lot again (I use your current theme) Nikola! In case it's helpful, one thing I've thought would be good for the fixed/floating panel is the Save button, when editing lots of copy it would be nice to have Save visible (zero clicks away) all the time (just as 'Latest updates' etc is in your current theme).

Yes @MadeMyDay re Javascript and interesting thought re Ajax injected fields.

One more thought on forms (which I'm guessing you have already had), for a future release of the module perhaps, the ability for portions of the form to programatically appear. E.g. if a tick is ticked then a bunch of optional fields appear. Apologies and even wider grin if this is already part of the module I've found this programatic facility valuable when designing forms with WuFoo.com This is not a request (you do SO much as it is!) just noted in case it's helpful one day.

Hi Ryan, Just a thought, this has probably already been suggested or goes against the approach you take for new pieces of core PW functionality but just in case it hasn't and it doesn't, I just again used http://flourishlib.com/ in a PW project to easily give me "2 days ago" (etc) when comparing dates. I noticed flourish has a ton of value-add for forms and so just thought I'd note it here in case it helps directly or indirectly now or one day. Thanks again so much for the up-coming forms module and I cannot say often enough how delightful it is to build with PW, it literally leaves me happy from my ability to 'make functionality'.

Quite superb. Thank you very much indeed Ryan!

Understood; thanks!

Thanks @Ryan for the super-fast fix, I looked at git but couldn't recognize it, is it one of the 8th Sept commits (not that I need it 'now' just trying to improve my git familiarity)? While the action for making first child is less easy than the others, I still love this approach; so intuitive and clear for users. And it's good to be reminded pages parents can be changed in the Settings tab

Thanks @nik for convincing me I wasn't only seeing my own finger trouble, I am sure I was partly doing the wrong thing but I did repeatedly end up with a page that previously would highlight if clicked and now would refuse to highlight (unless I refreshed the page). If I get clearer on precisely what I am doing wrong or what I am seeing that is wrong I'll post back here.

Hi fellow PWers, Too long since I did some PW work... Setting up a new site I just went to drag-drop some pages about and I found that 1. I was not able to make a page a child of another parent (maybe finger trouble) 2. more importantly, the ability to click on a page and select it (reflected by the change in colour) dies after a failed drag/drop and will not work again; until I refresh. It sort of feels something like the Admin uses latest jQuery from a CDN (content delivery network) rather than a named version and the latest version has a bug or is showing up a bug that an earlier version masked. Anyone have any pointers or seen this and knows more? Thanks in advance for any comments, cheers, -Alan Of course, now I've posted I am appearing to get good results. I wonder if it was because I was assuming I can drag anything anywhere (in the default vanilla site)? I'm now wondering if I was hitting a template-based restriction..?

Thanks for that suggestion Soma and +1 for that specific error Ryan (as if you've nothing else to do ) Could not work out why resizing would not work, as noted, changed my image field to single and problem gone. Thanks guys for your helpful posts. Cheers, -Alan

Thanks @DaveP, I'll look at those too.

Drat, left the UK for Canada so the cost would likely stop me as it would have a flight bolted on. But that aside this is great news! I'd be very likely to attend a venue nearer to Ontario if that happened one day.

@thomas Thanks for this, I will take a look and maybe change to this code as my implementation does not have the weighting you've got here. Cheers, -Alan