SiNNuT

For genres, types and stuff like that the best way is to also make them pages and then reference them using a pagefield on your resource template(s) @diogo , I was thinking Lister as well, but is this already publicly available?

Of course we can, but you did not mention what kind of resources you already digested. There is a Hanna code thread . There's also http://modules.processwire.com/modules/process-hanna-code/ . grrrrr

Well done

You could probably come up with a module or inputfield/fieldtype that can hold some of the most common stuff like http://schema.org/PostalAddress But for example http://schema.org/Person ,there is just too much stuff that is or isn't aplicable dependent on the project at hand.

I'm not sure a fieldtype/inputfield would be able to handle this elegantly. Sometimes you want to use microformats, another time you might need/want a scheme form schema.org with microdata markup. The data to represent persons and/or businesses/organisations isn't always the same.

You could be right but just for fun, have you tried setting it to let's say 1000 or even disabling xdebug and see if it runs?

I think it is because the live hosting is running an antiquated version of PHP. You should check if the version =>5.3.8 PW uses blowfish hashes for the password system if available. A PHP version conflict between dev and live servers, where dev has =>5.3.8 and live has not, will generate the notices you encountered in my experience. Instead of trying to work around this it would be best to ask the hoster to upgrade.

http://cheatsheet.processwire.com/#sanitizer

Something like?: //populate a PageArray $articleList = $pages->find("template=article, limit=25") //next $page->next($articleList) //prev $page->prev($articleList) This assumes your articles have their own template. You can put more options, like sort, in the page selector. The http://cheatsheet.processwire.com/ is always a nice thing to check for options available.

Great stuff Ryan!

PW should and would remove stale session files. In some cases this so-called garbage collection does not work, especially on Ubuntu servers. Adding a couple lines of PHP to config.php solves this problem for most people. more info here: https://processwire.com/talk/topic/5796-session-handler-database-do-not-delete-old-sessions/?p=56596

maybe this by teppo: http://www.flamingruby.com/blog/taking-apart-a-simple-textformatter-module/

It's either what adrian said, the destination parent page does not allow pages with the template of the page you are trying to move, or the template of the page you are trying to move has a setting for 'Allowed template(s) for parents' that restricts you from moving it. Have you checked all of the template settings on the family tab of the templates involved?

This sounds like some typical .htaccess rewritebase stuff. Look in that file for pointers. Also try searching this forum because the subject of installing PW in a subfolder and whatnot has come up quite often.

Yeah..beardscarfs ftw

Understood. Very common for large organisations to ask for an (sometimes ridiculous) amount of references. Let us know how things go.

You read the specification book and you already decided PW could meet te requirements. Just out of curiosity, what is it that would really test and/or be special for PW in this case? Volume of pages, concurrent users in PW backend, heavy traffic?

Are you sure it does not work as expected? For example, the url: http://processwire.com/skyscrapers/path%20with%20space also just shows to the homepage (processwire.com) content with the requested url still shown in the adress bar. If you check the response header however, it does correctly set 'Status: HTTP/1.1 404 Not Found '. It just a matter of how the 404 page id is configured i think.

Have tried $session->logout() maybe combined with $session->redirect($url) Make some PHP logic that says "if user is logged out show a login link or if user is logged in show a logout link. Also: https://www.google.nl/search?hl=nl&q=logout+site%3Aprocesswire.com%2Ftalk will give you alot of info on possible ways to get it just the way you want.

Yes, it's good practice to have far future expire dates. I don't think filename revving should ever be a core feature because of this though. It all depends on how you work and the frequency of when filename revisions would be needed. Some people use some kind of build tool/process that takes care of the filename revving, some might do it manually on pretty static sites where css/js/img changes happen sporadically, and others use maybe a module like http://modules.processwire.com/modules/all-in-one-minify/ which has 'automatic filename versioning' all ready to go.

It's kinda hard to tell what you mean. Maybe https://processwire.com/talk/topic/4420-page-list-migrator/?fromsearch=1

No problem. Please note that ProcessWire (PW) automatically creates the name from the title you enter. You can see this on the settings tab of a page. Where you can also edit the name should the need arise. PW pagename creation in the admin follows these rules: all characters except for these ASCII characters: "a-zA-Z0-9_." (not including the quotes) are removed. It also truncates the length to 128 characters. Spaces are turned into "-". Uppercase is getting lowercased and letters like "é" or "ô" are turned into "e" and "o", so: title:Great Pagé ! -> name:great-page

No, $page->name is used in the url of a PW page. Spaces are not allowed in a url. What you are probably looking for is $page->title.

Yes. CSV (comma-separated values) needs a delimiter. This can be a comma, tab, semicolon or more. I haven't used this module for a while, but i think you can (or may need to) add a very first record as a header containing a list of field names. Furthermore, read the options the module gives. So the CSV something like this: title,myfield1,myfield2 titleA,myfield1_value,myfield2_value titleB,myfield1_value,myfield2_value titleC,myfield1_value,myfield2_value