Soma

Yeah I think there's maybe some strange hidden chars but it's not. Just found out by try and error, that if the title has more than 50 chars it will break a title=string search... If you strip the title of the page(s) to 50 chars this it works: $title = "Sabine MeyerAcademy Of St Martin-In-The-FieldsKenn"; So, there's maybe some internal title searching that strips title in the query. But anyway, nice to know, still you should try working with names.

Maybe someone else more clever can explaing this behaviour, but wanted to say the doing this with title search maybe also isn't the best way. Why not use the page name when importing? This is more a reliable way as the name can't be duplicates and isn't fulltext. $title = "Sabine MeyerAcademy Of St Martin-In-The-FieldsKenneth Sillito"; $name = $sanitizer->pageName($title); $p = $pages->get("name=$name");

I explained why ( I think ) If you use %= or ^= for the title search and not title=value it will work.

Or since the title is fulltext search? $pages->get("title%=$title"); I recently think stumbled over something similar. I installed your db and get it to work with using %= or ^=. Not exactly sure what it's all about.

Sorry if it's a stupid question, but why do you have pages with the same title? Something seems wrong or it's just me. I can imagine if you search for title with a get() and there's multiple to be found... usually it would just return the first found... Not sure if it would make a difference but what if you use $pages->find("title=$title")->first(); ?

Or just this echo $config->urls->assets;

Can you put this in a template and post here what you got? echo $config->urls->root;

Then what js script are you talking about? How do you access it? I always use absolute paths from root without domain and it works fine.

You should be able to access it with /site/assets/myfile.txt

After updating to latest dev all my local installs on php 5.2 stopped working without any error, well just the general "Unable to complete this request due to an error." No error logged in PW or in PHP. So I'm kinda lost here to what the problem might be.

Thanks nik. No Markup Cache isn't installed. I also deleted caches, no luck. Don't know about APC if that's even running on that hosting.

My DataTable process module would be a good place to start. I've shared it mostly for others to use as a base. It's not a finished complete product, but more of a proof of concept. Since the needs are always different it's hard to make such a module work for all cases. I'm using a modified version on a online shop with hundreds of products. It's easy to change what cols are output and adding filtering by templates or categories. If you are comfortable a little with php and js you'll figure it out, or just ask away in the forums if you need help.

Ok, when I have php 5.3.8 with latest dev. I can't login and get this error on login page (login form isn't visible) Compile Error: Can't inherit abstract function ConfigurableModule::__get() (previously declared abstract in WireHookable) (line 32 of /[removed]/wire/modules/Markup/MarkupCache.module) When I set php to 5.4.10 it works again.

That also mean from now on PW doesn't work with prior php 5.3? I updated PW and got an error, but nothing logged or indicating what the error is. I finally also updated to php 5.3 and installed fresh PW and it now works. I'm also for going forward and php 5.3+ is cool, but there's some hostings that still run ~5.2 and I won't be able to update from now on, until they update php. Edit: just seen my hoster has updated and I can run php in 4 different versions.

If the /faculty/ template does have access rights set, yes then it wouldn't work as you get the page explicitly with get("/faculty/"). But for children when I remove view access for a role they won't show up in navigation unless you explicitly check the option to show them in lists and searches.

I would keep the structure flat and use date sorting. Moving posts from a "show on front" place to a "archive" place is most always not a good idea, in PW the structure is reflected in the URL and the URL of the post will change. So if someone linked to the post it will break (though there's a module that solves the issue with url redirects but it's questionable). To have an archive state for a post defined by a structure, where you have to move pages around, is something I would avoid generally. Having content live in a /archive/post1/ structure is always questionable, and if choosing to design such urls it would be done soft using urls segments. In your scenario I would keep the structure "flat" of the posts and if you want to define posts that show up on a up-front page, use a page field to select and sort them. Then render this page list out.

In the modules forum. Too lazy to link to on mobile.

Speaking of images manager each image is a page.

Use page fields and youll be able to select a page image or a parent or multiple. ImagesManager doesnt restrict but help.

I always start blank and do my custom css with some exceptions. For me layouting is easy once you know the ins and outs and css frameworks mostly just get in the way for my needs. And for special things and micro layouts they never provide what I need anyway. That of course is from a guy who does website layouts since over 15 years.

The CustomPageRoles module is alpha, proof of concept and it says that pages still will be rendered in navigation. You'd have to exclude them when cycling the pages in the loop with $page->viewable(). But implementing this check in the modules manager would get kinda complicated and result in some potential problems with how it all works together. The MarkupSimpleNavigation is access aware, but CustomPageRoles doesn't exclude pages when using with find() or children() calls, that's why it doesn't work also with MSN (heh). You can do use page_roles (page field) to do what you want with a simple check for user roles simply with this: echo $treeMenu->render(array("selector" => "page_roles={$user->roles}")); Because of the use of a selector you have to add and define page roles for all pages you have in navigation. It's not using the viewable access method, but simply checking the page field for if any of the user's roles is added.

No no, I meant that maybe this Module is the problem.

Do you have ChromePhp logger installed?

Yes.

If youre logged in youll see also unpublished pages?