DaveP

All sounds pretty sensible to me. Users are only pages, so a few thousand shouldn't be an issue, I wouldn't have thought. This may or may not have any relevance - https://sites.google.com/a/pjrprojects.co.uk/sitesguide/google-sites/how-tos/create-a-poll-using-google-forms

First line should be $staff = $pages->find("/about-us/meet-the-team/, include=hidden")->children; i.e. $pages->find rather than $pages->get when you are looking to return an array of pages. See http://cheatsheet.processwire.com/

@Soma, is there an easy way to get this module to play nice with AIOM, with regard to an option to inject the js or not?

Now, that I find interesting. A friend and I were talking the other day and we agreed that the refereeing had been consistently good - letting play flow and only blowing the whistle when absolutely necessary. Was it just the odd game, totoff, or do you have a different opinion of the refereeing overall?

As a supporter of Suarez's club team, I am somewhat used to his lunacy, and this piece http://www.theanfieldwrap.com/2014/06/suarez-bites-man-think-words-write/ just about sums it up. This, however, is more like we'd like him to be...

I quite often use Chrome & Chrome Canary so that I can be logged in to the same site (PW sites or others) as two different users, and to avoid even trying to be logged into 2 Google accounts in the same Chrome instance. The only problem is that, by its very nature, Canary can be 'unpredictable', shall we say. Best thing is to use Chrome & Firefox and avoid all the problems. FWIW, Craig, I shouldn't go out of your way just to accommodate oddballs like me.

Just as a by-the-way, don't waste your time using Chrome to test this on localhost - chrome.cookies fails for localhost domains, because it won't work (Chrome bug/'feature', not this module).

You definitely need /site/templates/admin.php

@Craig, thanks for this - just the job for a project I'm on at the moment. Installed on PW 2.4.4 and seems to be working fine.

So long as you can navigate around your site, then everything is fine. It looks as if your hoster changed some Apache settings as well as upgrading PHP.

I recall back in the days I was using Joomla (or it might have been as far back as Mambo), and I installed a file explorer type plugin, which immediately gave me access to every hosting account on that server! Needless to say I soon moved away. While that was a long time ago, there are clearly some servers are still badly misconfigured and it pays to be vigilant.

500 errors are almost always .htaccess related, and yours looks no different. Usual course of action is to comment out sections until you find the culprit, but from the error message you quote, this should not be difficult. What changes did you make immediately before this problem appeared?

Here's a fun recipe... Install https://play.google.com/store/apps/details?id=eu.apksoft.android.smsgateway on an old android phone with a cheap sim with plenty of free sms messages. Expose the phone's webserver using https://pagekite.net/ (might be a bit of a challenge) (PageKite has been mentioned here before. Thanks Marty!) Send sms messages to your heart's content.

Update - Just downloaded latest dev version and everything is behaving as it should. No idea what was causing the problem (it occurred using a slightly earlier dev version). Anyhow, everything is good, even if it is Friday 13th!

Really look forward to seeing the live site. The big icons for Servicing, MOTs etc. look very good.

Tried all the above, to no avail. However, I did notice in the DOM there are 2 instances of <ul class="WireTabs nav" id="PageEditTabs">, which contain different content. They aren't in the page source so I assume they get injected by js. I would be surprised if two with the same id was intentional / desirable.

Nothing in the console. <silly question>Having never used this field before, what is the output supposed to look like?</silly question>

I'm getting some weirdness using a PageTable field. After adding a row, the backend output is messed up.

The whole law/regulation/directive/whatever was completely ill-conceived in the first place. And the ICO's handling just as shambolic. They have done one U-turn after another. On balance, it is looking as if your approach is the best one, Pete.

Hmm, cstevensjr and 3fingers have covered exactly the ground likely to cause these issues. Having googled around, and please forgive me for suggesting this, are you absolutely sure that you are importing the db structure into the new db and not the old one? The reason I ask is that that is one way to guarantee duplicate keys, because they would of course already exist. (And we do all do things like that occasionally.)

How did you export the database? Give us a quick description of the steps you took to export & import, with any tools used.

...and thanks to you also, for your insights and for taking the time to share them.

I think I understand what you want. Something like this very pseudo-code should point you in the right direction... <?php if($input->post->passkey == $page->passkey){ // Show for-your-eyes-only content // and perhaps set a cookie to allow viewing of content unhindered in future } else { // Show form asking for passkey (using method=post to avoid inadvertent sharing of passkey in url (with Miss Mountshaft?) if we used get) action=<?php echo $page->url; ?> }; ?> You will obviously need to wrap some proper php and html around this and perhaps separate bits out in the cause of DRYness.

http://leafletjs.com/ is well worth a look - I have used it recently with PW, as have others - https://processwire.com/talk/topic/6073-wwf-species-tracker/#entry59374

As far as I am aware, 'notice' and 'warn' level errors are nothing to worry about, however there are 2 lines (464 & 465 in the first block) that are actual 'error's. There is, I think, a known issue with tildes (~) in PW urls, so a search of the forum may turn something up. Otherwise, I would concentrate on those 2 lines, do some Googling, and see what you come up with.