apeisa

There is some setting in config.php about db table name Cases. Check it out fellows.

Soma, did you get the same error with Shop-for-processwire? You run on 5.2. also?

Thanks Soma. I think AngularJS looks pretty cool and examples are super simple: http://angularjs.org/ - that is also pretty neat introduction (just hover over the blue background code to get more information). Will definitely to take some time to examine more of these libraries. Oh, and your (hopefully soon released!) module looks great!

Thanks for reporting. I think you are fine now. What php version you are running on server?

Yep, I agree: knockout.js tutorial is one of the best I have been playing with. How you find learning knockout.js? Easy - hard? I've been thinking that next thing to learn should be some JS-framework with dynamic data bindings, like knockout, ember (http://emberjs.com/) or angular (http://angularjs.org/)

This looks great - will take this on the test run tomorrow at Avoine's Vihti Office.

"Custom coding" might be as simple as this: <?php if ($user->hasRole('subscriber')) { echo $page->body; } else { echo "<p>To read full document, you need to login (or register)</p>"; echo $page->shortContent; }

Glad you got it working Dave.

Added the Teppo's fix for repeaters!

Roles are actived per template basis, so take a look at your home template and access tab. PS: Welcome to the forums!

Step 8. from readme: That being said, you do have sc-checkout.php on your temlates-folder?

It would. Just not too simple. I find it amazing that there isn't a single open source editor that takes different approach - but there are many editors that are tied to single commercial app (like mad mimi etc). Something like mindplay was talking about here: http://processwire.com/talk/topic/2103-problem-with-tinymce-in-chrome/#entry19695 I'm all in to help contributing in a such module, if there will be a community effort. I believe it is much more JS than it is PW or PHP, so it would be wise to open source it as independent software. Then it would be tied deeply to PW to provide unique and top notch editor. It could also integrate some other editor for basic editing options (links, headings, tables, lists etc).

Yep.. kind of. No visual preview, no drag and drop, no clean ui, no resizing of images etc.. It takes much more to create nice and simple UI for that use case.

One useful solution to RTE madness is to handling image/text-positioning outside the actual editor controls. You add "image&text" blocks and position images in relation that single block text. Madmimi has nice implementation and can be quickly seen on their home page video: https://madmimi.com/ In my opinion most work for client comes from A) Image positioning B) Tables C) Pasting word document which isn't cleaned properly, has some styles that aren't even removable from editor etc. I think A and B can be solved with good editor (images like mad mimi, good table editor like CKEditor or Aloha). C can be solved with "clean all styles" methods.

Great thinking mindplay! I agree that this is one of the major pain points on system that alter the database schema on-the-fly. I think your solutions is pretty similar that Laravel has (altough there it won't record those migration files, since it is pure framework, you would just write them). But system would run those on right order based on filename date.

On the other hand, it gives nice focus on page name (url segment) when creating, but allows it to be "hidden" on settings tab later on... I have not heard any complaints from clients about that 2-step process.

I agree with Deane - it would streamline the new page process, specially on those cases where template is predefined (like it mostly is).

Fixed.

Thanks for the report Martijn. This has been on TODO list way too long, will fix it now!

I have also stumbled on $pageArray->count many times.. it would be nice little tweak to make it same as count(). Like parent and parent() etc.

+1 to findRandomInterval() Also, agree with Mindplay here - a great addition and many times more useful than "total random"!

I don't see any reason to add more settings that are totally irrelevant or purely aesthetic for 99% of projects. Urls with trailing slashes look nicer (imo) and work nicer (like Ryan explained). Overthinking and overconfiguring each possible option is certain way to bloat. Page that isn't allowed to have sub-pages might be allowed to have sub-pages later on. Also the family tab settings are only for admin usage - children are possible through API. So I wouldn't tie any code breaking functionality on that setting and assumption.

Hi Deane and welcome to the forums. I have never removed the title myself, so not sure how pw behaves on this situation. But take a look at the "family" tab on template settings. It will allow you to choose that template "people" can only have pages with template "person". This way when you add pages under "people", those will be automatically "person" and no template dropdown is shown. Now that I took a look my person templates (usually actual users, since those are pages too), I use title always as a "fullname", and have separate fields for Firstname and Lastname. Maybe you could do a hook other way: parse firstname and lastname values from the title? Tip: you can edit the title label and description on per template basis: so title label can actually be a "Full Name" on person templates - and you can also put a description like "Write lastname first, ie. Meikäläinen, Matti" EDIT: I'm way too slow

Still doing it, without dev tools opened. Versio 23.0.1271.64 m

I'm on 22 and it's not gone. Chrome is updating currently so interesting to test soon.