doolak

So it doesn't came from server-side - well, somehow yes, but fortunately from ryan-side ;-)

LOL - i was about to ask here where you all see those links - and now when i scrolled above, i saw them too... So this has to be something on server-side - i cannot imagine that all of us have such a spyware on different platforms and different browsers. Strange stuff... Edit: @MatthewSchenker - in your post Happy New Year is not linked, but all others are now. So we'll see what happens...

Does the Form Builder support Multilanguage?

In some cases it would be nice if one could have the option to pre select a page when adding a Page field - especially when you are using the Page field to generate a "normal" form input, where values can be chosen - not really "content pages". Here e.g. i have used a Page field for a set of radiobuttons to choose image alignments: In the field "Bildausrichtung" (German for "Image align") you can choose between "centered", "left" and "right". In this case i wanted to have the option "centered" preselected - and in my opionion this would be a nice addition to the page field - which maybe even will not be that difficult to implement? For the moment i have solved this with a module which uses jQuery to preselect the field - but if you just could choose this when adding the page field would be great!

Happy New Year from here too!!! Wish you all good health, happiness and success for 2013! And please keep on doing that great work with ProcessWire!

Perfect - thanks, Ryan!

Great addition, Ryan!

Wow - that works! Thank you very much! I have just a minor issue left: If i add a script as follows, it adds this script at the top of the included scripts in the admin page and it seems that JQuery has to be loaded first. (I have done a test with loading jQuery too with that module, this is then added a the top and it works fine.) Is there a possibility to add the script at the end of the included scripts? My actual code is as follows: <?php /** * ProcessWire 'Admin jQuery' * * ProcessWire 2.x * Copyright (C) 2010 by Ryan Cramer * Licensed under GNU/GPL v2, see LICENSE.TXT * * http://www.processwire.com * http://www.ryancramer.com * */ class AdminJQuery extends Process implements Module { public static function getModuleInfo() { return array( 'title' => 'Admin jQuery', 'version' => 101, 'summary' => 'Add costum jQuery to the admin theme', 'singular' => true, 'autoload' => true, ); } public function init() { $this->config->scripts->add($this->config->urls->AdminJQuery . "adminjquery.js"); } }

Thanks, Pete! So that seems to be better and easier than using a admin theme... i just had a look at such a admin theme (never tried one before until now) and i guess my idea above will not work in that way without using a complete new admin theme, right? Or would it be possible to have just a addition to the default theme in that new admin theme? But what you explained would make that unnecessary - if it's possible like that to add code at the admin theme this would be of course the best way. So if i understood it right, i would have to use $this->config->scripts->add() in a module to add the JQuery to the admin template, right?

Right now i guess i recognized how it could be done in the easiest way... I think it will be the best solution to add that jQuery by adding it to a admin theme - just have to digg a bit through that and find out if then it would be necessary to use a complete theme or if it's possible just to add the necessary code to the standard theme. But as some themes use some of the files of the default template this may be possible.

I thought about maybe using a module just for that "hook", something similar to the HelloWorld.module or the MapPageField.module - so apply the jQuery after the page is saved or better, rendered. Just don't know how to add code to the head of the admin page, the HellowWorld.module uses $this->message() but i would need something similar which makes it possible to apply some Javascript in the header...

How can i use jQuery for such a case without "hacking" the core - can this be included through a hook?

Would it be hard to implement an option to delete all the files at once?

I just had a look at the CSS classes of the backend - yes, that would work i guess. Same like Ryan mentioned regarding the Form Builder in the thread i posted above.

Just in the case that somebody else is looking for a solution to disallow upscaling like i was right now: I just read this thread and thought about using one of the functions above - then i found another thread where some options which were recently added to the PageImage class were discribed: http://processwire.c...tion-questions/ Even cropping direction was added now: http://processwire.c...ons/#entry22535

Right now i found this thread: So it seems that it is already on the Roadmap. Great!

There are a lot of scenarios where i would like to use such a conditional logic - one e.g. could be the following: I want provide a repeater where you can choose an image, set the alignment and an optional linking to the big version of the image or an internal/external link So the repeater fields would be like that: 1. Image field 2. Page field to choose alignments 3. Checkbox if should be linked to bigger image 4. External or internal link The linking to the bigger image will work automatically if the Checkbox is checked - i use the Fancybox for showing the image. If this option is checked, the 4. option does not make any sense - clicking the image cannot work as a link and show up the fancybox at one time. So it wouldn't matter if the client provides that link in option 4 if the conditional logic is set in the template - but to avoid confusion it would be nicer to show this option just if option 3 is not checked, so a conditional logic for the administration would be great. That's correct.

Well, i guess this is a very complicated feature which would take a lot of time to implement it... But - if one day this would be added that would be really absolutely amazing! BTW: does the Form Builder support conditional logic?

Thanks for that hint, diogo - this seems to be an option and is very useful in general.

I agree absolutely - i love the fact that ProcessWire does not affect the markup in the way a lot of other CMS do - so i think it's really better to use an extra field for the image alignment setting, because in that way the developer can specify the markup himself. Same for the possibility of setting a link to a bigger version - here it's the best if i can specify the markup myself. Regarding the resize option i am a little unsure - of course i can use an extra field where the client can enter the width and the hight, or maybe just one of them. But as the markup for showing a picture in another size than it is saved on the server does not give us much variations, i wouldn't mind to have such an option in the ImageFieldType if this would give the client the possibility to see live how the size is changed and resize it by dragging, like in TinyMCE. Another advantage would be that resizing could be handled proportional and the client is not allowed to enlarge the picture bigger than the original size. And as nothing else could be generated than a markup like width="x" height="y" i don't feel that it's that uncontrolled affection of the markup we try to avoid through the CMS. If i would have the option to decide, if this resize option is shown or not - this would be perfect. Edit: It would even be possible that the "resizer" just collects the two values and we have still full control over the markup. Yes, i usually do it like that.

Will there be the possibility to resize an image and set alignment manually - like it is provided when you add an image through TinyMCE? Is something like this planned for future releases for the Inputfieldmage? I usually provide an extra field where the client can choose between "left", "right", "centered" and "none". Same would be possible for the image size, but it would be nicer if the client could do that "on the flow" with having the possibility to preview the size. Cheers, Christian

Yep, i had to smile about myself, too ;-)

Yes, i have checked it again, too. There is not such a possibility. In some cases it's fine to use the fieldtype "FieldSet", so you can e.g. have 3 fieldsets. But in some cases it would be fine to have a specific maximum amount of possible repeater items, which can be sorted etc. - but should not be more than that maximum amount of elements, e.g. to fit the layout limits. So this would be a nice feature to add i think.

Strange - now i added a new "FieldsetOpen" field and a FieldSetClose was added automatically. Before that didn't happen, don't know why... (maybe i just did not recognize it somehow). So my question is answered: The FieldSet (Close) is added automatically. Edit: I tried to reproduce how it happend and i guess i have added the FieldSet (Open) and didn't recognize that the FieldSet (Close) was added automatically. Then i tried if another FieldSet (Open) would work as FieldSet (Close) and because it did not work in that way, i deleted it - and i deleted the automatically added FieldSet (Close), too - but didn't recognize that it was there. So it was no bug in there somehow in a special scenario - everything works fine!

Hey there, it may be just a silly mistake by myself, but i cannot find the fieldtype "FieldsetClose"... They are not displayed in the dropdown when i add a new field. Any ideas what's going wrong?