arjen

Don't focus on the title, focus on the files. Go to github, switch to dev branch and download the zip. I just checked and the zip seems to be the latest dev version.

It's not labeled as stable, but it is pretty stable. I run it on one site without errors. Ryan also runs it on his bike website - I suppose without errors. If you use git you could check your current branch to be sure. When using a zip I would recommend checking a file like this which is recently edited (2 days ago) and compare that with your download. This way you know it it's the latest version.

What if you rename or delete the file?

I have yet to discover one client who didn't prefer ProcessWire over WordPress after a 5 minute demo. Another quick fix would be to let a prospect talk to one of your previous clients. Let them tell the prospect how they work and how little time they have to spend to actually edit their website instead of wandering around a (looking beautiful, but UX wise dramatic) backend. ProcessWire is point and click and it does what a client expects.

That would be really great. Seeing how to structure things like this, might be helpfull to others building less sophisticated systems. It also shows why ProcessWire isn't your regular old CMS and how powerful it can be.

Great info and superb presentation! As a number addict myself I really dig this kind of info. Also very nice of you to show ProcessWire in the footer. Would you consider writing up a case study on how you approached this excellent website?

Not yet. I is scheduled on the roadmap with the release of version 2.5+.

Thanks for your answer, I also learned that it differs slightly from one group to another.

Looking great! Nice subtle "Arabic" looking background too. Care to share how you get the Gebetszeiten/Prayer Times? You use an API?

Vineet, thanks for explaining. Martijn's ideas sound fine to me.

I've read your sentence a couple of times but I have a hard time understanding it, Vineet. What is an user email id?

Short answer: if it has to scale without a known limit use pages. Let's say a log module which saves pages with user login info you use pages since this might scale up to a large number. If you are creating a slider/carousel with a couple slides you can use a repeater. Also if you have to use the API extensively you better use pages since you can use selectors or PageArray to sort and filter data.

Welcome to the forums dwimar! 1. Login to ProcessWire and go to Modules page at the top. Find the Login Throttle module and click on the title. A new page loads with several options. You can change the settings here. 2. Which version are you running? There were some issues with Page::localUrl before so you might want to make sure you are running the latest dev version.

I didn't read your post carefully, my apologies. When a user succesfully logs in you could store a cookie with the path "/" (so other sites can read it) with the user ID. When on another site you can check if that particular cookie is set and automatically log them in. This is not really secure since fetching a cookie with an user ID is fairly simple. You might want to add some layers of security. Perhaps someone else would know how to correctly deal with this.

Welcome to the forums, Adones! I did some research and crossdomain user accounts are not really easy/straightforward. I'm not even sure if this is a ProcessWire thing, If you make any progress on that area I would be glad to know!

I don't think "gallery" is a proper selector. Either you use /gallery/ or something like template=gallery. $pages->get('/gallery/')->url; $pages->find('template=gallery')->url; Does $page->$albumimage->url really work? Shouldn't this be $page->albumimage->url?

You also should turn on debugging in your config.php file under /site/.

Double check if ownership/rights are set properly. Are the files really there? I see a public_html2? Can you install a clean version of PW just to check if it works?

What version of PW are you running? There were some issues solved in one of the later dev branch commits. You might want to check that out!

I remember Hani build a selectbox fieldtype while ago.

Offcourse thanks to ryan too! Great work as usual! Your programming is really great to follow and great to learn by!

Couldn't agree more, diogo! Great concept and superb execution.

OrganizedFellow, holy *** that Emmet stuff is pretty awesome! Thanks for sharing!

Thanks for your time soma! I will look into this tomorrow. Perhaps the $f->repeaterFields route isn't the way to go.

Thanks soma! That was a typo. It should be $fields. I updated the code. Regarding the: $f->repeaterFields->add($field); I'm not sure I'm following you. How can this be converted to hold multiple fields? When trying to add one $f (field) I'm getting an error: Fatal error: Call to a member function add() on a non-object.