Soma

The user has the language set. if($user->language == "en") ...

google.com "processwire.com session files" -> http://processwire.com/talk/topic/1142-lots-of-sessions/

I got same error and empty cache folder did the trick. Same as a modules refresh in admin.

Have you tried delete /site/assets/cache/...?

Still don't know what browser... I missed that you wrote it works in default theme, and I took a second look at the main.js. There's been a small change to the click behavior of the sticky button. I pushed an little update to both master and dev, let me know if that fixes the issue, although it still works as before.

Have you deleted cache? /site/assets/cache/ ? I don't know why MarkupSimpleNavigation wouldn't load.

Also wanted to dive in and say hello. I like coffee. Seriously great stuff, and you're right my DataTables module is only an example and it was a rough coding session never found any more love. But actually to just read and list data with quick edit link in a modal, which is nice for when editing sets of items, and I'm using it in some projects. It would also support inline editing and stuff but never found the energy and time to give it a shot. Making everything configurable and modular/abstract is quite some work, so all the love for people taking this "concept" further. I think there's a need for such things and I love seeing other people getting involved with PW module development. There's so many good things that can be done and PW makes it so easy. But dude that Handsontable is a real beauty and looks like a great concept and API! Keep it up. Thanks for sharing. The right tools make a big difference. If you need a beta tester...

It's a common error in coding and has nothing to do with PHP. I would write the loop and current class like this: foreach($categories as $category) { $class = $category === wire("page") ? ' class="current"' : ''; $out .="<li$class><a href='{$category->url}'>{$category->title}</a></li>"; } === is comparing the objects if they're the same in memory, since $category at some point IS the current $page it works. You could also write: foreach($categories as $category) { $class = $category->id == wire("page")->id ? ' class="current"' : ''; $out .="<li$class><a href='{$category->url}'>{$category->title}</a></li>"; } No need to compare titles as they theoretically could be same for another page. So the id is just as good and better.

Something that's in dev since 2.3.1 is that you can make the autoload specific. More infos can found here http://processwire.com/talk/topic/3768-processwire-231-dev-branch/ : 3. Conditional autoload modules. This is because if you look at your module, it will get loaded and hook added in init on EVERY request, even on front-end. So to make this easy you can use a selector or an anonymous function (php 5.3 only). To only load this module in the admin, you could then do "autoload" => "template=admin",

Thanks Martijin for you help also. It was fixed with value.toString() The "transp" is ok and it was the easiest way to keep backward compatibility. It would require to reinstall the module to change the schema, though it could also be done with a update script check. I don't see why transp is a problem. And just because of transparent making the data field to 11 chars instead of 6 is not nice at the end. But I'm not happy at all to add the prevent collapse issue, which is IMO a problem of the admin theme from the start. And since the default admin theme has no clearing on the widget content box, I'm fighting with this in various modules and custom admin pages and the admin theme. Resulting in the same fix in different modules and themes over and over again. Some solve it this way some the other way. It would be a easy fix in the core and I mentioned this so many times already that I gave up. This results in so many inconsistency now throughout the themes and modules, I hope with the new admin theme update in the future this will be fixed in some way.

The colorpicker has been updated to 1.0.7. with fixed and a new swatches feature. - Since 1.0.6 the colorpicker supports color swatches to add predefined colors for easy selection. Thanks @Rayden for the implementation. - It's now also possible to add a transparent default or swatch value with the string "transp". - fixed a bug with numeric values like 333333, 555555 which caused the colorpicker to not init correctly. A screen showing the swatches. Thanks for Raymond Geerts for the update and fixes.

Not sure if you got it working or not, but I did a quick test and you you're right it doesn't save formated fields like page fields. I got it working by creating a clone of the saved page and then uncache and get the page from DB to get old value. Now it also saves the page fields. public function saveReady($event) { $p = $event->arguments("page"); $p = clone($p); echo "new headline: " . $p->headline; // debug $this->pages->uncache($p); $old = $this->pages->get($p->id); // get page from db echo " | old headline: " . $old->headline; // debug // exit(); // debug }

I noticed this too, that it doesn't work when no key is set only label. Not sure about the \r\n, I think that's system dependence. I also noticed that if you enter 0 as a key (0:=option) it will not work with querying with selectors, as the data field is a text field and not a integer. YOu have to start with 1:=option to make it work.

Not error but notice. And debug mode on.

You use delegate events... in jQuery this is done now with .on() previous with .live() $('.container').on('click', 'a.editlink', function(){ $link = $(this); ... });

I'm also using dev and dev all over so that can't be issue. I meant more your browser Any javascript errors?

You can add any tinymce config to the field tinymce settings, look at the tinymce documentation what you need. Then enter them in the custom advanced config textarea. http://www.tinymce.com/wiki.php/Configuration3x:cleanup

Haha, Wanze is right!

Works fine here since ever, can you provide more details on your environment?

I proposed this idea several times already in various threads... right in the repeater thread once it was published. I played with the idea and even tried to work out adapting repeater module, but to no success yet as it gets a lot more complicated than first thought. Since there were no real response or interest I haven't spent more time with it. One try was also to build a block module, but haven't got the time to further develop this and it's in a proof of concept alpha stage, only front-end editing and not backend interface. Searching those seems one of the harder things to solve as it gets complicated, but if using a spider or something it wouldn't be a real problem. Scalability would be another consideration, as I can image people using this then to build vast websites with every block being a page, with repeaters inside resulting in even more pages. You get the idea.

Silence can't distract you, then you're empty... I'm full of things.

jQuery: $('li:odd').addClass("odd"); done.