apeisa

Jonathan, not sure I know what is not working in your case? Just tested this "echo $fredi->hideTabs('delete|settings')->renderAll();" on my install, and it works just fine (shows just children tab, editing and saving works normal).

1. Yep, page needs to exist before files can be added to it. Maybe simplified page add and then show edit link for files? I am not planning to support files in add view. 2. Hmm.. I don't see this as an issue. Editing and adding pages with Fredi should be used for editors only: it uses many of the same methods than PW admin does. Same goes for edit links. 3. Inputfields are responsible for cleaning the data.

You can't echo just hidetabs. $fredi->hideTabs("delete")->render("field") is way to go.

Can you post more of your current code on the templates?

Marty, simply skip using renderScript method and directly add the the stuff you need from there.

Thanks Bernhard, that should be safe change, just committed! I also added simple support for adding new pages. Current syntax is this: <?= $fredi->setText("Add new article")->addPage("article", "title|date|summary", $parent) ?> First parameter is template (required), second is fields (optional, uses only title if empty) and third one is optional parent page (uses current page otherwise). It doesn't do much, but works pretty nicely. It redirects to new page after successful save. Name is created from title.

Cannot reproduce that problem with settings. Which pw version you are using? About adding pages: for the one page add, we would need to have template and parent as required (parent could use current page is not set) and then bunch of fields. That should work.

I'll look into it. Some very early version of Fredi supported it, so shouldn't be that hard.

Sorry, there was clear bug. Fixed now!

Ah, I use the new config stuff there, so it requires 2.5.5 or later: http://processwire.com/blog/posts/new-module-configuration-options/ I probably should fall back to earlier method to support old installs and smooth upgrade... didn't think that at all

Damn, I haven't thought at all tabs that are added with autoload modules... It might be that it would still be better to have own "process page edit" instead using the same as core uses. I'll test and think about this little more. Thanks for letting me know Marty!

Haha. No worries

When do you see delete tab?

Thanks for testing it Marty! How do you like the new edit links? I cannot reproduce the delete tab issue here. It shows for you if you allow all the tabs? Do you use $fredi->hideTabs() method at all (not required though)? Interested to hear if that works.

While I was it, I decided to tackle the PageTable problem also. So now the version 1.1.1 works with PageTables also (it's modal inside modal, so not exactly the dream come true, but it works if you need it).

Just pushed version 1.1.0 to github. It adds options to hide tabs, but also new nice feature where edit area and links are shown on when hovering (fallback to normal links when using touch enabled device).

Just pushed version 1.1.0 to github. Please let me know how it works. I went pretty closely with Bernhard's original css stuff, I also added options to hide additional tabs. Although I have feature detect for touch, when hovering is not required to see edit links.

I like the idea of adding class into parent element and using that to hide/show/style the hover. I think it will work in most designs, but not all. I'll add that as option into Fredi.

Have you subscribed? I am sending more invites every now and then.

Page field is one to many or one to one relationship, depending on how it is configured.

Yeah, google gears should be the way to do it, if Java applets are not possible! On serious note, this would be great!

Good to know! Sabre looks very polished, so no problems there. I'll implement this on my project tomorrow.

Quickly tested this today (since I have need for it on one personal project). Very nice implementation and will definitely meet the criteria for my project. Few notices if lindquist or someone else goes further with this: - used new [] array syntax (but just once) - I removed that since I run on Ubuntu LTS (stuck with php 5.3 until update to 12.04). - no language tags (quick fix though) - recurring events are done by writing RFC5545 RRULE format, which is of course way too technical for most users. Does anyone know any JS plugin that would offer nice UI for that? Would make lovely inputfield. (This might be it: https://github.com/jkbrzt/rrule ) - sabre library is huge and only small subset of it is in use. Would some smaller library be enough, like these: https://github.com/tplaner/When or https://github.com/simshaun/recurr It was breeze to setup and works flawlessly. Admin ui is very snappy and easy to use. Nice work!

Joshua, what kind of feature set you are looking for?

There shouldn't be that kind of problem (I'm not seeing it). Can you send me with more information into my email and I'll take a look over the weekend. Glad you are liking padloper!