Soma

WOw great module already, very well done. It's quite long code to study, but I just went and am playing around for a little. I see there's still some way to go But still that's what's there is great! Love it. I experienced some weird things. The template created home_language has fields set from the default basic page template. I think it should not add (only title) to or may try implement something to select it when installing -- So far so well, now the template fields are not using asmSelect it seems, so I cant add or change them. Dooh!! -- So also it shows me in the template overview page int he fields col "6 home" which is strange and shouldn't be, only count of fields. -- And when I add a physical php template to it, I get an memory excaused php error from adminbar module when viewing page. Errm not sure why, haven't looked further at it for now. I strongly suggest now that you're throwing out a first cut version, to upload a git repository of this. This would help and other may can help easier. Also it's great for issues. I fear it can get cumbersome to manage all in this thread alone. Thanks again for working on this awesome thing!

Nice work on the site Nico! Sure must been fun and simple to build it. Hearing your concerns about files in PW, I was about to write something about regarding file management in PW. I got the same concerns as you and while working on a pretty large multilanguage site too, I came across some limitations when dealing with images in various ways. I'm thinking about this part for a long time now and can get my mind around what would be best and how to accomplish it so it suits PW philosophy. I think we should start an thread on another board regarding this. Do you mind starting it? Make suggestions and think about alternatives. It was discussed and requested already by some people. If you would give a try at it, I would love to help. I think the way it's currently done works and is great and simple for certain cases, but also is limited and not very easy to maintain. --- moved edited message to here: http://processwire.com/talk/index.php/topic,692.msg5216.html#msg5216

Great work on this module so far. I implemented the function like ryan suggested and it works great. I used this jQ plugin also in some project and it's a nice one. I agree with the feedback Ryan gave already. But since it's a WIP it's hard to give suggestions to current version since I don't know what's planned. Also since there's already many posts and I don't have the time to read and valuate all, aswell there's so many things and ways, options that it could need/have. I think it's a nice image extension for galleries, as I think using it for regular content (wysiwyg) images it's not suited. Just thinking loud, it need more love in the UI and having previews of the croped versions would be nice. But I think you already know that. Remembering the thumbs would be nice as if you edit/change an already edited it would be nice to start with the area already selected. Also autocrop was something that poped up in my mind imediately after trying. Would be nice feature like default croped image. Issues: Not sure if you are aware that when I upload (drag) it doesn't get shown, it stops for me by 100%. When I upload with dialog it works, but it doesn't invoke fancybox preview and crop fancybox function... so only after reloading page they work again. Some notice shown when debug on: Notice: Undefined offset: 1 in /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/site/modules/pwCrop/InputfieldCropImage/InputfieldCropImage.module on line 79 Notice: Undefined offset: 2 in /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/site/modules/pwCrop/InputfieldCropImage/InputfieldCropImage.module on line 79 Notice: Undefined offset: 1 in /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/site/modules/pwCrop/InputfieldCropImage/InputfieldCropImage.module on line 79 Notice: Undefined offset: 2 in /Applications/XAMPP/xamppfiles/htdocs/pw2.ch/site/modules/pwCrop/InputfieldCropImage/InputfieldCropImage.module on line 79

Thanks for your effort on this module. Unfortunately I'm too busy atm to check it out. Just from reading, I'm not sure if you are aware of the multilanguage admin feature Ryan is working on for 2.2 (~end year) here: http://processwire.com/talk/index.php/topic,598.0.html Not sure how this would take effect on your work here. May you want to make sure you could use some of what Ryan is implementing regarding new API stuff and such. Edit: just realized that this may not effect each other... not sure though if there could be some benefits. Question: One thing that just surprised me is why $Languages and not $languages, because it's like a constant?

This is easy. In the TinyMCE field input settings, you must add "tablecontrols" to your buttons and add "table" to the plugin field. More advanced: It would also be possible to copy InputfieldTinyMCE to your site modules folder and rename it to create a new Inputfield. From there you can modify everything to your needs without touching the core.

Hello ljones You don't need to echo everything, especially if its plain html. Also you may use the code tag: <?php ... for posting code in the forum. <?php is for highligthing php code properly . Since I'm so mad and am cleaning my own code currently, I was so crazy to clean up your code and made it as short as possible: <table width='100%'> <tr> <td class='room_no'>Room No.</td> <td class='cont_info'>Contact Info</td> </tr> <tr> <td> </td> <td> </td> </tr> <?php foreach($page->children as $child): ?> <tr> <td class='room_no'><?php echo $child->title?></td> <td class='cont_info'> <?php echo $child->ten_pri_name ? "\n<strong>{$child->ten_pri_name}</strong><br />" : '' ; echo $child->ten_first_name ? "\n<strong>{$child->ten_first_name}" : ''; echo $child->ten_last_name ? "\n{$child->ten_last_name}<br /></strong>" : '' ; echo $child->ten_website ? "\n<a href='{$child->ten_website}'>view website</a><br />" : ' n/a '; echo $child->ten_email ? "\n<a href='mailto:{$child->ten_email}'>email {$child->ten_first_name}</a><br />" : '' ; echo $child->ten_phone_no ? "\n{$child->ten_phone_no}<br /> " : '' ; echo $child->Media_Business ? "\n{$child->Media_Business}" : '' ; ?> </td> </tr> <?php endforeach; ?> <tr> <td> </td> <td> </td> </tr> </table> Or this is also possible to seperate html and php even more. <?php foreach($page->children as $p): ?> <tr> <td class='room_no'><?php echo $p->title ?></td> <td class='cont_info'> <?php $name = $p->ten_pri_name ? $p->ten_pri_name : '' ; $firstname = $p->ten_first_name ? $p->ten_first_name : '' ; $lastname = $p->ten_last_name ? $p->ten_last_name : '' ; $website = $p->website ? $p->website : 'n/a' ; $email = $p->ten_email ? $p->ten_email : '' ; $phone = $p->phone_no ? $p->phone_no : '-'; $mb = $p->Media_Business ? $p->Media_Business : ''; ?> <strong><?php echo $name ?></strong> <br /> <strong><?php echo $firstname ?> <?php echo $lastname ?></strong> <br /> <a href='<?php echo $website ?>'>view website</a> <br /> <a href='mailto:<?php echo $email ?>'>email <?php echo $firstname ?></a> <br /> <?php echo $phone ?> <br /> <?php echo $mb ?> </td> </tr> <?php endforeach; ?>

Congratulations on 5000 Posts!!! 170 Users!

Not sure. I thought it also gets when using sanitizer pageName. I think it should.

There's also setting that can be made in the InputfieldPageName module for converting chars, like ä to ae.

Yeah, don't know how can I missed it. I almost forgot about symlinks and that it's possible... I just created core pw folder on server for the 2 projects running on it. Works as expected.

That's some good sound in my ears. Can't wait to see something like this in PW This will for sure simplify module management. But I still don't really understand git well enough to be a help with it decide what would be best. I just know how to simply manage a repository... @ryna Also nice to hear symlinks can be used to have one rep of modules for multiple PW's on the same server. Are you linking the whole module folder? Would this be possible with templates aswell I guess or the core?

Thanks Ryan for the Tip. It's an After Hook. I will later test this again with your suggestions.

Ah sure now I get it Ryan (didn't see the there was a label) ... though this doesn't seem to work in IE8. I got it working in IE8 with the following changes. I did a condition for < IE9 and do a click event on the icon, that would then toggle the input checkbox. The routine to toggle field I moved to a function which get called by both versions. I tested in IE8 and IE9 and it works. New InputfieldFile.js attached. You may want to change your PW source with this or make further testing? InputfieldFile.js.zip

Back to topic. I looked at the InputfieldFile.js where the delete ui handling is. I don't know how this even works in other browsers. It's delegate checking for the input checkbox to change, and sets the inputfield status according if the input is checked or not. The input itself is display:hidden! So, I can't click an element that's not visible... If I make the input display:block, the checkbox input is visible and I'm able to click in IE. I'm currently trying to get a workaround, but it's not as easy as I first thought. I'll have to consider it a little more...

Thanks for testing apeisa. Then it must be something with my EditHelper Field Link module I guess, where I had to set a clearfix to the inputfields containers... will test again with deinstalled. EDIT: Yeah it was it.... My module does modification to the fieldwrapper to be able to put an inline element... But since it's only used for superadmin... no real problem for now. As for the top save button, I just left out the button duplication in IE, as mentioned in the other thread.

Thanks for the offer to help adamkiss! Would be greatly appreciated to get it work in IE8. Client is in a network and can't install other browsers. As for IE8: - It's impossible for now to use PW in IE8 at all. The edit page layout is messed up totally!.. (tested this in IE9 switched to IE8, and tested in IE8 native on browserstack.com ...) - and the mentioned problems with delete file and topsave button.

I agree with what being said. There should be more shortcuts and easier access to things. I already started doing something for when on page edit screen. http://processwire.com/talk/index.php/topic,470.0.html Dropdown menu for PW I implemented in my Teflon Admin Theme, to shorten ways. http://processwire.com/talk/index.php/topic,530.0.html

You're welcome, glad if I can help. Thanks for the applaud 8) Not sure what exactly you want to archive... on template settings tab? I remember a related subject in this thread first page... http://processwire.com/talk/index.php/topic,414.0.html

$tmpl->nameContentTab = 1;

I fixed some issue with the module not working on TinyMCE fields when editiing a page on deeper than 3th level. For some reason the FormSaveReminder.js which does the checks, was then getting applied after all the tinyMCE scripts and thus not working. (on higher levels it was appended before them) It took me many hours to realize this was the problem What's up with this Ryan? I did now change it to get inserted through str_replace just after JqueryCore script. I'm not sure how future proof this will be, but I guess the JqueryCore will never change. Latest version is now on github. Thanks EDIT: Just found that in Firefox it doesn't work with TinyMCE Fields at all... Firefox is almost like IE now, crap...

Hi and welcome to PW forum! since it's a field on the page, you get the selected page reference using something like this <?php /* make sure the inputfield i.e: "userpage" setting is set to allow only 1 page */ // get selected userpage url echo $page->userpage->url; /* if inputfield page is set to allow multiple selected */ // to get first echo $page->userpage->first()->url; // to get all foreach($page->userpage as $userpage){ echo $userpage->url; } Written in the browser, so could contain errors.

You can get user created and modified for a page with <?php $page->createdUser->name; $page->modifiedUser->name; $page would be $child in your code

It could be done easily in the core, but most flexible I found is to copy tinyMCE Inputfield to site folder and rename it. Since bramus_cssextras can be used to parse content.css automatically it makes sense to have it outside core anyway. I'm using it like this now in my projects. I came to the conclusion, if we gonna make this in core you would have to extend everytime again when in need of a new plugin/feature.

Thanks antti for testing. Yeah IE9 seems to work, it's IE8 that causes problems. Since there's no support in PW for < IE8 it should in fact be < IE9, or honestly I would be all in to drop IE completely even. But there's client's not able to install other browsers in a company environement as we all know. I'm sure there's a simple solution to this in IE8 to get delete function working, but then I think there's a lot more we didn't find yet. I think this all should be addressed as soon as possible on how PW will continue regarding browsers support. It was a bit unlucky that I wasn't aware of this before, and found only out after the client already failed and lost content he entered already.

There's seems to be another problem with IE, (or at least IE8). Deleting images using the trash icon doesn't work in IE. I don't have an IE currently available to test this. But client changed to Safari and it's working, so definately a problem with IE. Anyone having IE can confirm this? Since there seems to be popping out various problems with IE, how far is this really tested? Considering most client use IE, it seems PW is not really usable with IE.