Soma

Just installed on latest PW21. Thank for this great addition! Works so far. Just one thing noticed (using chrome at least) when using this input type on a seperate tab it's bugged. It doesn't show the text until i click and select all it re-appears. This doesn't occur when using this in content tab.

Just for when developing in PW it could be handy to... ... see the name of the field when hovering the label on page edit ... have a direct link beneath each field when editing a page that brings me directly to the edit field page. I imagine this would be a simple module. Any help to start such a modul would be appreciated. Thanks, Soma

I think I spoted a minor problem on the sample site when installing new PW21. There's internal links that don't work. One on homepage "read more" (Basic Site Profile) links to a page that doesn't exist, and two others on /about/what/ are id tags {~root_url}, {~page_5813_url}

I also was shocked about the 1meg. Quite a bummer. ExtJS alone is beyond imaginable, and that just for quick edits. Let alone the complications that can occur. Well it would be possible to run your site jQuery in a seperate namespace and make sure your JQ loads before Aloha ones... headache granted – Well in first place I was also thinking about doing something simple self brewn, that fits into PW. Just discovered Aloha few days ago. I thought it may usable but also sensed it may overkill and too akward to implement, use. Not to mention depend on it. Yeah images would be extasic. Lists? Small? Paragraph? Are you planning writing a wysiwyg in this case? Or using tinymce? Also what are you seeing will be the way to define what fields are editable on page? Something that's controlled in by the template file would be cool. BTW: I already hear a "Oooooh! my text is screwed, I copied from Word into the page!"

As always, much appreciated! Already on my watch list. I can't wait to see how this evolves. I think having a way to build simple or even more advanced forms, is a very welcome addition to further speed up the process. "Everybody" hates building forms manually. EDIT: Oh and new version tested, still works!

I finally tried this module out, and it still works in new 2.1! Thanks for the example Ryan. But it throws an error if it's saving the form as page: Exception: Method Page::removeRole does not exist or is not callable in this context (in /wire/core/Wire.php line 231) #0 [internal function]: Wire->__call('removeRole', Array) #1 /site/modules/FormTemplateProcessor.module(198): Page->removeRole('guest') #2 [internal function]: FormTemplateProcessor->___savePage(Object(InputfieldForm)) #3 /wire/core/Wire.php(267): call_user_func_array(Array, Array) #4 /wire/core/Wire.php(229): Wire->runHooks('savePage', Array) #5 [internal function]: Wire->__call('savePage', Array) #6 /site/modules/FormTemplateProcessor.module(237): FormTemplateProcessor->savePage(Object(InputfieldForm)) #7 [internal function]: FormTemplateProcessor->___render() #8 /wire/core/Wire.php(267): call_user_func_array(Array, Array) #9 /wire/core/Wire.php(229): Wire After commenting out the following line in the ___savePage() it works and Page gets saved as child of the form page: $this->contact->removeRole('guest'); I have only tested with standard text, email, textarea fields. Would be great to may have this developed further. What are the plans on this? This is intended to be for the admin only? Or would it be possible to have clients build a form in this way?

Not sure, the code looks right. I'm using similar code right in front of me. $child->imagefield->url which returns url of image. On a side note: You could also use only one full image field and create various sizes on the fly like: $child->image->size(0,150)->url // max height 150, but keep ratio But maybe you already know that and want to have the possibility to have a different thumb picture than the full.

You're right thanks! I was confused as the script wasn't working because I made a error and I checked what the $page->pagefield_radios returns...

How can I get the page object, which was selected in the radio box list? $id = $page->pagefield_radios; // page field with checkboxes - returns id of selected: 1183 (as string?) $cat = $pages->get($id); echo $cat->title; // returns nothing echo $cat // returns 1 (id of root Home) $kat = $pages->get(1183); // id entered directly echo $cat->title; // returns correct "Acryl"

Well no I got a problem with the Page recovered, it doesn't show up in navigation on page. When I go edit page it says: "This page is in the Trash", How can I fix this? EDIT: Just figured changed the status to 1 in the DB, it shows up again. Is this all that is to it? EDIT: Just noticed all childpages also changed state to 8193. So I lost all status information of the pages (some were unpublished or hidden). :-\

I experienced something strange once I deleted a few pages. Suddenly I realized I deleted wrong page with lots of subpages, so I wanted to open trash to recover it. But I couldn't open trash, it loads and gets stuck, so I can't do anything anymore. I went to change parent id of the page I wanted to recover manually in DB, it worked and page is there again, but trash still doesn't open. I remember having deleted two pages using same name I created earlier, may this caused the problem. Well after empty trash it work again. Can't really say what happened or recreate it.

I have a template that only can have a certain template as parent. But if I have pages set up, I still can change the parent pages template to use another template, it doesn't throw an error.

As title already says. When I want to drag-move a page as a child of a page that has no childs yet, I can't. Even if the target page has childs but isn't opened, I can't move it.

I'm playing with this input type recently, and it gets cumbersome to use, when each time I select a page the tree closes. If I want to select some pages from a certain branch, I need to repeat to open the same over and over again. Would be nice if it's possible that the tree stays open when adding pages.

Recently was thinking, if it would be possible to use the HTML5 features to make an easy front end inline editor per field for PW pages. Check this: http://aloha-editor.org/ Haven't checked it out deeply, but it may even fairly easy to implement that on top of PW.

Found the issue: $page->filesManager->path - doesn't return anything, it should be: $page->filesManager->path() - this works I changed this in ProcessPageEdit.module to be $this->page->filesManager->path() and now upload works.

But when sharing the files through a resource page, it would then only be possible to inserting them in tinymce, not for image fields on page? So what if I like to have an image field allowing 1 image, to be able to be on a predefined place on the layout, and which is not language specific?

Just thinking. How would we handle images then? upload again on each page?

The approach of having the languages in one page with multiple fields, can be nice as it's all in one place but to work well it requires some things to be considered and it might not as flexible as with separate tree approach. Concerning the urls for search engines in the field approach, I don't know how easy it would be to have PW use a "name" field for each language separate. So for a german page it would have "/firma/ueber-uns/" as the path, while english it would take the english names and result in "/company/about-us/" for the same page. To have PW and in template know which language is currently viewed, there would have to be some url segment defined that is used like domain.com/en/... or optional have subdomains. en.domain.com. At work we often need to create multi-language websites, and there's always some sort of restrictions, problems, workarounds needed depending on system and which approach is chosen. So if there will be some strong and flexible core support for building multilingual sites, it would be a great selling argument as almost all other opensource systems lack good implementation.

Hard to say really. Parent, order, status as you said I think for sure. But now I'm thinking about custom fields that's used for additional statuses, I'm thinking of the ones I need to create for each template because core doesn't have it the way I need it, like "not_in_navigation" checkbox and "not_searchable"... So if possible, there should be a way to add custom fields that needs to be synced on a template basis. I think it will be easier to find out once a first alpha can be tested.

it's doomed to immortality... just created an issue on github for Ryan ;D https://github.com/ryancramerdesign/P21/issues/45

this is for targeting IE versions in CSS by simply being able to use it like: .ie9 .title { ... } .ie8 .title {} without the need of hacks or conditional stylesheets. looks like the site uses html5boilerplate, see their website for more infos on this subject.

Thanks apeisa, well it's still a prototype version with dummy images. Some are too small and just scaled to fit.

Thanks Ryan, glad you like it. Also, fixed the strange url behavior when using non hash urls ,when coming from searchengine results.

I'm aware of this, just not sure yet how to handle, working on it... I know, but ajaxy doesn't support his new history.js yet, which supports HTML5 history and gracefully degrades on older browsers using hash's. Using history.js alone wouldn't work, beacuse it doesn't support multilevel, forms and json out of the box. I d'love to hear about other ways doing this in a simple way if anybody knows, cause I've read that HTML5 history ist buggy and inconsistent across browsers...