thomas.isberg

Thanks! I read the forum thread and realize that every website that need to be updated deals with this issue, since editorial content is likely created on the live server. I only thought of the problem with my users, since I'm in development phase and make every update locally before I publish live. Thanks also for your tips from Google!

Hi! I have a website where users register and become members. Naturally I create a PW user for every new member, and use PW's login functionality. I want to go live with the website, but also want to continue development. I have a lot of ideas and would like to update the website with new templates and stuff once a day for a few weeks now, and then maybe once a week while adding new features. I usually export my entire local database when I update the website, and then import it on the server. But if I do that, every new website member on the live website will get lost. Does anyone have a good idea on how to approach this? I thought about exporting all the members to file before I import the new database, and then import them again, but: a) It just doesn't feel safe. b) I can't figure out how to set their passwords right during import. Export gives me hashed passwords. Cheers and thanks! .Thomas

Thanks Ryan, yes I needed the pagination.

Thank you Ryan, you are absolutely right!

Thanks Soma! Does that actually work? I knew that array value was unsupported by has_parent, but didn't think about the possibility to put several has_parent conditions in there. I'll try that. Thanks, .Thomas

Hi! What's the best way to exclude pages with an unpublished or hidden parent anywhere in the hierarchy? In a find() that is. Thanks! .Thomas

Hi! I have multi language all set up and working with multi language fields and two languages: default and english. Everything's working, but when I create a new Page and try to set title and title_english, only title is stored. The english version comes in blank. Here's what I do: $item = new Page(); $item->template = $this->templates->get("page_complex"); $item->parent = $page->id; $item->title = "Kommande matcher"; $item->title_english = "Upcoming fights"; $item->save(); Any ideas anyone? Thank you Ryan & all for this wonderful CMS!!! Cheers, / Thomas

Hah, cool. I'm looking forward to your FieldtypeRepeater though, Ryan. I think that approach would be beneficial in cases where you have very page specific blocks of content, and maybe just one "widget" on the entire website.

Absplendifabtastic! Thank you both!

Wow, thanks diogo! Didn't see your reply before I wrote my essay. Your solution could actually work! Gotta run now. Will check in again soon! Cheers, .Thomas

Thank you Ryan! Haha, no "widgets" doesn't really provide the details... Hm, after rephrasing this reply a couple of times... Here's what I want to achieve: Create different blocks of content (widgets) which can be added to a page. Each page can have zero, one or several blocks. In my example the list of blocks will populate a column to the right of all other content on the page. The blocks will all share the same width, and each block will be placed underneath the previous block on the page. Kind of like a banner area on any website with advertising. This does not affect the PW solution though - a block could be presented anywhere on the page. That'll be up to the template. These blocks can contain different types of content. One might auto generate a list of the latest blog posts. That one could either be completely automatic, but it could also require the administrator to define which blog to generate the content from, if the site contains several blogs. In that case a list of available blogs should be presented in the admin console. Another block could present x number of products on sale, with image and some text describing each product. In that case the admin console should present a list of available products, and allow the aministrator to add as many products as desired. Ideally these blocks should be re-usable on any page. The products on sale should be the same on all pages where that block is used. However, as a starting point I would be happy just to achieve the possibility of adding blocks of content. If the administrator has to put the same content in several places, so be it. . The benefit of using blocks instead of simple template content then, is that the administrator can change parts of the page to display something completely different, without changing the template and the fields required by that template. Now, the examples above (blog posts and products on sale) are for background. What I need help with are these parts: 1. Creating the functionality to add as many blocks as desired to a page. I really want the administrator to manage these blocks from the page edit view. A FieldtypeMulti in a separate tag is probably the way to go. 2. Say that I want to create a block which puts two lines of text on the page. The admin console should simply present two InputfieldText instances. Now, I'd rally like to use existing Inputfields in the block's Inputfield, because then I can tap into their functionality, and the possibilities should be endless - a block could easily contain just about anything. Oops, gotta run! I'll check in again as soon as I can and read through this reply. Don't know if what I wrote make sense... Cheers & thanks! .Thomas

Hi, this PW looks like great stuff! Great work you guys! I'm trying to find a solution for implementing widgets on my pages. For starters, I'm trying to create a simple widget which just requires two InputfieldText instances in the admin. Now, I realized that I could create a template for the widget, and then add widgets to a page by creating child pages based on that template. I could then check for child pages using that widget template, and render those into my page instead of linking to them (as with normal child pages). That works technically, but I don't like to idea that the list of child pages becomes a mix of actual child pages and in-page widgets. How would you guys implement this feature? Would you use templates for widgets, and somehow alter the way the child pages are listed in the admin? Is there a way to present the widget child pages in a separate tab within the page editing view (and not display them in the Pages view, and not in the Children tab)? Or would you create a Fieldtype which can hold multiple values, and an Inputfield which presents multible GUI elements? I've spent quite a lot of time trying this approach, but I can't get the values from the two InputfieldText:s to be sent when saving... I managed to read values into them from the DB though... However, that was achieved without extending the InputfieldWrapper, and I'm guessing that some important PW features went missing along the way then... Any advice? Cheers & thanks, .Thomas