alan

I am on a 2.4 site and a search (in the Admin, the built-in Admin search) for Knowable in order to find instances of wrongly spelt Knowledgeable has no hits, even though the word is in a textarea on a published page. Any ideas why that would fail (I assume it's not a stop word due to length and uncommonness)? Ditto searching for "wearing your swimsuit" (it's on a page and there's no hits). [it's as if the default mode is the admin search only searching Page titles perhaps?]

Just used this on a 2.4 site and it looks like it is working AOK (only noting that since the listing does not mention 2.4 compatibility). I've probably said it before, but this Module provides functionality for which there is in my view a good case for including in core PW. Providing a DRY way to manage assets is very valuable. The only 'big' thing I would love to work out how to provide, via this Module I assume or via the image or file field, is an easy way to swap a file for a replacement. This too I think has been a big-ish discussion before and I think it's not as simple as I am assuming. All I know from management of a large TextPattern site is however that a centralized place to see all assets and from where you can easily re-upload a new version or a file or image is a real boon. Oh for enough spare synapse that I could add this functionality myself and give back to the community, sorry I'm too thick!

Hi Russel, welcome to PW Yes you need the .rb file if you are using Compass and you're right implying that there is nothing 'special' to do to make Compass & SASS play with PW. One easy way to start is to build the HTML (CSS, SASS, Compass) for a static page ignoring PW to check you are happy with your implementation of those technologies (that they work) then set about slicing up the one HTML file and replacing it with PW. For example at it's simplest getting PW to render the content of the TITLE tag to check the page outputs the static HTML parts and the new PW part (the TITLE tag) all the while keeping the structure all good for Compass and SASS. Once you have this sussed then it's just a case of how you build your pages (templates). There is a FAB site to deconstruct and learn from, I can't recall which it is :/ sorry, but I think it's the skyscraper site. You may want to buy CodeKit if you've not done so already. This is a huge topic and mine is a little reply post so sorry not told you more or specifics, but bottom line PW is completely agnostic of your mark-up, CSS etc and it will work BEAUTIFULLY with Compass, SASS, Susy (Susy is superb). Good luck and enjoy

+1 JeffS for schema.org, I certainly switched to this microformat after umming and aaahhing after reading this book http://goo.gl/RYLQTx [Amazon excerpt] . I also changed the way I use HTML 5. But add an HTML 5 debate to an SEO debate and you have your entire life used up right there

Ditto Joss, my understanding is META KEYWORDS is, since it is so utterly abusable, dead and unimportant and unused by anyone while TITLE is highly important and META DESCRIPTION is valuable. But totally defer to Roope re AdWords using them.

Exact same reaction as you ankh2054 when I stumbled across PW (thanks to Marty Walker whose site I found and saw PW mentioned). I have not regretted or looked elsewhere since and I have actively re-built some sites from other CMSs to PW JUST for my own benefit. Welcome and enjoy!

Hav you turned on debug in config.php? That invariably tells you something sometimes everything you need to know.

Hi tobaco, Soma is the King of this so I can't be sure of the following but my guess is that for some reason the initial attempts to list all Modules failed (e.g. a glitch in the Matrix) and so you initially saw 10. My experience of this Module has been that it is 100% reliable across multiple sites. I think when it connects and lists all 224 (and counting) it stores this list locally and so until you next manually refresh that list will remain. So I would expect for these reasons you will find this Module very robust going forward; unless there is something else happening here with the particular install/environment. Edit: PS: DOH! Misread your reply, though you said "so this seems to be only a temporary problem fix" - sorry, sounds like you're all good and don't need any comforter comments like mine Enjoy PW it's been a revelation each time I've needed it.

More fallout from 'rights' problems - Modules Manager is not able to update the first two Modules I tried it with. Had various "cannot write" errors which I fixed with judicious use of 777 and all errors now gone. But still modules report as not being latest and updating them (from Modules Manager at least) just does nothing. FTPing: for me the *only* fly in the PW ointment. I must attract flies :/

Thanks Teppo. I'd always assumed that was OK, but twice I've done that and it breaks stuff :/ This latest time I found at least one place where that happened: I set each folder .../assets/cache/form-builder/form-1 (not recursive) to 777 and when I did form-1 it broke (the form went 404) so I returned it to 755 and OK. So I still feel a little like I'm treading on egg shells when I FTP up a PW site in a way I didn't with say Perch or Textpattern. Since this is the single fragility/criticism I* have (*I am sure others must not have this problem so I wish I knew what it was with me!) I have almost nothing to complain about and a massive amount to be thankful for -- give me this FTP oddity of mine with PW any day and I'll take the PW route *every* time; I just hope one day to understand what I am doing wrong or how my MAMP Pro setup is wrong or how my use of Transmit is wrong. The site is AOK now after the hand 777s so all good. If that's what it takes next time then I am totally happy -- ideally I would just like a list of the perms for ea directory in say /assets/ that could cause a problem or a guide to them, so I know what to do next time and have no need to trial/error.

I go this too. I read Ryans comment and used my FTP client to recursively set all contents of assets to 777 and it solved the problem. Thanks Edit: Uh oh, spoke too soon, that cured the error seen in Admin but gave me Bad Gateway 502 on the public side... Edit: OK, my fix was: 1. turn on debug 2. use FTP to NOT recursively set all to 777 but from errors shown in the login screen, set folders to 777, I had to set (from memory, I think): assets cache files sessions LazyCron.cache assets/files/-all-folders-here assets/cache/form-builder (404 if not) BUT also set assets/cache/form-builder/form-1 to 777 and that produced 502 bad gateway, set it back to how it was and all OK. This is the SINGLE thing that I feel fragile about with PW, publishing and permissions. While there were a great many things that 'hurt' with other CMSs I did find uploading to be 'easy' - export the DB, import it, upload all files. Done. I would LOVE to know what should be the perms for the folders in PW, probably all I need to know is /assets/* since it seems I have found some (all?) of the right settings but I would like to be sure for next time. Does such a thing exist (i.e. that tells me making .../form-1 777 will kill the for and put it back to 755 etc)?

Solved with 777 on the sessions folder and all contents. I seem to hit this (it feels) every time I make a site live :/

Wrong place to note this probably but I also noticed IMG tags are P wrapped (which has me questioning the best semantics...) but assuming I don't want IMGs P wrapped (like here) and assuming I find a CKEditor setting to stop this (one of these maybe), is there a place in PW I can go add a config setting to change CKEditor (I am hoping in .../templates/... somewhere so it's safe from Module updates)? In case relevant I already use these two custom locations to get CKEditor to do lovely things in inline mode in PW: cc-styles-CKEditor:/site/templates/scripts/InputfieldCKEditor/cc-styles-CKEditor.js and /site/templates/styles/InputfieldCKEditor/cc-styles-CKEditor-inline.css Tks lots for any pointers! Edit: For now, finding instances of [P IMG /P] with this and dragging them up with CSS to stop the wrapping P making the IMG look too low.

Thanks Ryan; I checked and both ACF and HTML purifier were enabled. I'm puzzled how that (DIV) happened. I *was* pasting from Word but knowing what a pile-o-vomit Word is made from under the hood I am 99.9% sure I pasted to my go-to plain text app, as I invariably do, and then copy/pasted from there. Also I am puzzled as I am pretty sure when I used the CKEditor button 'Source' to see what was there, the first time(s) it showed a P with a SPAN with inline style (not the DIV?). Weird. In case relevant, I'm using the inline CKEditor and your/the super-nice Customer Editor JS styles and CSS file. I'll watch for it happening again and see if I can spot anything more. And tks re the tip re deleting old 4.3.0.

It appears that CKEditor on Chrome at least is able to jankily add STYLE when not asked to. At least while editing some copy I noticed a P that looked wrong (too large) so I selected the whole line (treble click) and chose 'Normal' from the 'Format', but initially it would not switch to 'Normal' but stuck at 'Format' (not 'Normal' or 'Heading 2' etc). I checked the source and it was <div><span style="font-size:1.4em; line-height:1.2em">My lovely text wot I rote</span></div> I checked Google and found this CKEditor and Chrome issue. Does anyone know if this is likely the cause? If this is the cause anyone know best to apply it—I am on 2.4 with the CKEditor Module (1.1.7 - latest) but under the Module folder there seems to be two config.js files: ckeditor-4.3.0. and ckeditor-4.3.2? Thanks to any clever peeps!

+1 For Pete's suggestion up there ↑

Love this Module Pete, thanks a lot! This + Field Dependencies is simply making the admin experience powerful and simple—Fab!

Thanks again for the simple PHP 101 Soma! Perfect! PS: I had been print_r'ing and seeing the content of the array in both conditions (with and without pagination) and not realised that although both were arrays with data only one would **return** something and that therefore I could do a simple test! I've learnt more than I expected, thanks again and glad I asked

Thanks Joss, there is a loop further up I'd ignored since the comment that it came with made me not think it would be testable for this (in fact I had not yet worked out what it did exactly!). I have used the code from everfreecreative's great post as a starting point in the making of this hence. It's been excellent I'll go back and look at that for loop and see it it's as simple as that and either way, thanks for the suggestion!

Sorry this is likely such a simple question, but if I've got some happy pagination code like this: $out .= "<div id='galleryPageN'>" . $a->renderPager(array( 'nextItemLabel' => "Next", 'previousItemLabel' => "Previous", 'listMarkup' => "<ul class='MarkupPagerNav'>{out}</ul>", 'itemMarkup' => "<li class='{class}'>{out}</li>", 'linkMarkup' => "<a href='{url}'><span>{out}</span></a>" )) . "</div>"; that is working AOK. But I want to detect when the pagination will or will not be present in order to render or not render the holding DIV (I want to avoid an empty DIV). I am sure it's got to be a simple piece of PW+PHP testing $a to work this out but I've been tripping over trying to work it out. Thanks if you've time to ping me a comment back on this, cheers, -Alan

Short tip Use the ajax powered search to find pages you want to edit—it's a super-fast way to get around the admin. Longer (but same) tip I was on the cusp of not writing this because it is likely so obvious to so many, but just in case you are like me in terms of navigation in the Admin for editing pages... In PW 2.4 the new search makes finding pages lightening fast. While some themes from before 2.4 was released display recently edited pages to help speed navigation, the new default theme in 2,4 doesn't; and I missed that a bit. But the new search is super fast so now whenever and wherever I am in the Admin, if I want to edit a page I just type in the search box, it ajax-pops, one click and I'm in the page ready to edit—no need to visit the page tree Thanks to Ryan and crew for this small but great advance OK, back to work.

I'm glad I started this thread now! Thanks for the edits Soma; So many times you've helped, VERY grateful!

FAB! Thanks Soma!

Oo... That looks like a nice exercise to go through, thanks SO much Soma!

I am pretty sure I will find they are (I hope!) once I get started—thanks for the offer, but as you say, only when you get a minute! Cheers!