Soma

Thanks Hani, but nothing like this. I've been looking into it right now more closely and it works for other fields, and the thing is it works only for textarea language TinyMCE fields. Normal Textarea TinyMCE fields it is broken and doesn't work and html get's stripped out. This is with dev 2.3.3. I'm currently trying an update.

With MSN this could look like this: $nav = $modules->get("MarkupSimpleNavigation"); // topnav $current = $page->rootParent(); // current root page echo $nav->render(array( 'max_levels' => 1 ), $current); // subnav echo $nav->render(array( 'max_levels' => 1 ), $page, $current);

A co-worker asked me what the problem could be, as the html of a normal TinyMCE textarea field gets stripped out completely. - Configuration of the field is all correct. - Turning on/off the content type html or unknown doesn't have any effect. - I then tried to hook into saveReady and echo out the value, and it has no html at all at that point. - Also hooking into before FieldtypeTextarea::sleepValue the value already has no html when it gets there. - Changing Browser doesn't have any effect. - It's a PW dev install I think 2.3.4 or 2.3.5. - I never experienced this or know of anyone here having that issue. Any ideas what to look for or try? There is no other modules or hooks that would interfere with textfields.

The "fix" is just for something that is shown when debug mode on. I see, but you can actually grab that new module from github and upload it manually. Rare case, and I update minor version usually.

It is up to date 1.0.9 is latest, but I didn't bother upping the version number for such small warning fix that I did shortly after commiting 1.0.9. m If you would install it new you would get 1.0.9 with that fix in. There's not separate version/copy or repo on the PW site, so it's getting it always from the github repo anyway. Or am I wrong?

It's not an issue but a warning. I commited an update that removes this already some time ago.

Also wanted to note taht the new Admin Theme is broken on many things (especially the new dropdown) on IE8 and not that usable/nice. Not sure how that matters at all, but we still have clients that use IE8.

To the above post. ui sortable is screwed because of the addition of overflow-y: scroll on the body. It's a known bug I ran into even couple years ago and seems still there in jquery ui. pff Once you scroll the page and start dragging a item, it is offset by a margin and not on you cursor anymore, makes it impossible to drag sort or scroll. Once you remove the overflow-y: scroll from the body it's all good again. Not sure what else could fix the problem, as removing overflow-y: scroll on the body will bring back the content jumping on dropdowns that are longer than window.

But you don't need the $page->setOutputFormatting(false); and $page->save() parts, and it is only temporary and lasts for the one request.

Admin pages can have segments and they're mapped to the function in the process module attached to it. But that's not the urlSegments you can use on frontend. Like /adminpage/edit Will call executeEdit() method in the process module. I'm not sure how custom admin pages work and that's maybe not possible as you don't use process module to make the admin page.

That's why I made a module long ago "FormSaveReminder". It's still beyond me why this feature isn't yet in core.

Don't you know ModulesManager?

No theres no unpublish($page, true) You can use the Batcher module to mass edit pages. You'll need a selector like "has_parent=1004" id of parent... The behavior of children of a unpublished parent is the same as when it's published. It doesn't influence it's children. Hard to say without seeing your code. But my guess is you have a script that tries to find the parent page but can't because it's unpublished... and you call $parent->children() somehwere but $parent isn't really a page object. that's what the error says at least. But you still could get the parent and it's children via API even if unpublished, you just add "include=all" to the selector or just use a get $parent = $pages->get(1004); // id of the parent $children = $parent->children(); // works as usual, even if $parent unpublished But it's still unclear to me what you try/need. Why unpublish them, when you want to query them? That's a question I can't really give an answer, as I still don't know the reason why you want to unpublish all those pages? Do they need to be hidden in navigation? Where hideing the parent would be enough? I can imagine that if you really want to make them all unpublished and not reachable to unpublish the parent for the branch and control a 404 in you templates init somewhere like the head.inc. if($page->parents("status>=". Page::statusUnpublished)->count()){ throw new Wire404Exception(); } Basicly checking if any parents of the current requested page ist unpublished, and then show 404. But not tested really, just a example.

I don't think he needs to do anything, but ModulesManager and Core modules manager (download/install) I reported issue on github for this. I got it working by cycling all modules and calling their $modules->getModuleInfo(modulename); which will not install the module but init it. This is the only way I found to still be able to call getModuleInfo on the module after downloading to check for requirements and show install button or not. Because now both modules manager are missing this step and just show install button. It is no problem on the listing (table view) as there is all this happening already and checked for "requires".

I just noticed some warnings with imagesizer when I have debug mode on.. The image sizing seem to work though, but seems odd to have so many warnings shown on frontend. Notice: Undefined variable: thumb2 in /xxxxx/core/ImageSizer.php on line 370 Warning: imagejpeg() expects parameter 1 to be resource, null given in /xxxxx/wire/core/ImageSizer.php on line 370 Warning: rename(/xxxxx/site/assets/files/1016/fv1b7390_kl-1.600x0_tmp.jpg,/xxxx/site/assets/files/1016/fv1b7390_kl-1.600x0.jpg) [function.rename.php]: No such file or directory in /xxxx/wire/core/ImageSizer.php on line 384 Warning: iptcembed() [function.iptcembed.php]: Unable to open /xxxx/site/assets/files/1016/fv1b7390_kl-1.600x0.jpg in /xxxx/wire/core/ImageSizer.php on line388 Warning: chmod() [function.chmod.php]: No such file or directory in /xxxx/wire/core/Pageimage.php on line 210 Notice: Undefined variable: thumb2 in /xxxx/wire/core/ImageSizer.php on line 370 Warning: imagejpeg() expects parameter 1 to be resource, null given in /xxxxx/wire/core/ImageSizer.php on line 370 Warning: rename(/xxxx/site/assets/files/1016/fv1b7281_kl-1.600x0_tmp.jpg,/xxxx/site/assets/files/1016/fv1b7281_kl-1.600x0.jpg) [function.rename.php]: No such file or directory in /xxxx/wire/core/ImageSizer.php on line 384 Warning: iptcembed() [function.iptcembed.php]: Unable to open /xxx/site/assets/files/1016/fv1b7281_kl-1.600x0.jpg in /xxxx/wire/core/ImageSizer.php on line388 Warning: chmod() [function.chmod.php]: No such file or directory in /xxxx/wire/core/Pageimage.php on line 210 Also wanted to mention once again, that sizing images that already have the desired dimension it fails and no image is shown. Like $image->size(940,0)->url and if the source image already has 940px it fails and no image shown. This is now since a long time and has been reported and is (very) annoying

What? Making a page unpublished counts only for the page itself. Depends what you need and what you mean with hide. Lots of options and contexts and terms...

I think you don't need to set it. It will automatically take the template name without .php To set a filename other than its name you need to set the alternative name.

I want 15.245px Just noticed that when I have images field in a custom tab as the only field (is at top), the grid view doesn't work. At least for me in latest version Chrome. ©licking the icon just collapses the field.

I pushed a little update to 1.0.9 fixes dependency issue with extending module that isn't installed yet installing module now only possible if requirements are met by the module info some changes to the module table columns and showing summary directly, added "added" date column and number of likes from users module dependencies now shown below summary if any.

I'm not sure the date is really recognized as date and that would work with strtotime() but maybe you should put it in as a string: $p->calendar->find("booked=0, checkin_1='16.11.2013'"); This should definately work $date = strtotime("16.11.2013"); $p->calendar->find("booked=0, checkin_1=$date"); Outputformatting has nothing to do with it.

That seems a problem both ModulesManager download/install and core Modules "New" download/install suffers from. Problem seems to be that calling getModuleInfo() inits the module and since ProcessLanguageTranslator isn't installed yet, it throws the error because the class isn't loaded. I fixed it with a little workaround. So it will disable installing when there's requirements that aren't yet met. I pushed an update to ModulesManager just now. Also with some little improvements to the data table.

The htaccess surely isn't the problem here. How is it only when you use it in a tab or also when used in normal content area? Strange, And do you have site installed in a subfolder from the root?

You could install the modules required by adding another rule to info array "installs" => "ProcessLanguageSupport" or "installs" => array("ProcessLanguageSupport","AnotherOne"); That will install those modules before yours. Or you can install them in the install routine of your module simply with a get() call wire("modules")->get("ProcessLanguageSupport"); From the perspective of modules manager I'm not sure I can add something that would check. I'm interested what happens when you install your module using core "New" feature. You enter your modules class name and it will ask to download it if found.

// prependFile: Filename to prepend to output, must be in /site/templates/. (default=$config->prependTemplateFile) PageRender.module #302 $output->setPrependFilename($config->paths->templates . wire('sanitizer')->name($options['prependFile'])); It runs the value through $sanitizer->name which doesn't allow "/". So no it's not possible.