bluemultimedia

Thanks matjazp! That helps!

I ran into a weird problem with the WireTempDir (site/assets/cache/WireTempDir). A client uses cheap hosting that still works well with ProcessWire. But it does for some reason have a file & directory count limitation. And after reaching 260.000 files and directories the file system becomes read only. After some digging, I found that the site/assets/cache/WireTempDir was responsible for about 99% of the reported directories / files. It seems like the temp directories were never cleared. Now: I don’t think this a general ProcessWire problem, as I have other sites, that have an empty or – at least – not as full WireTempDir. Are there automated cleanup operations that may not be called due to some weird hosting issues? How are those dummy directories usually handled?

Thanks for the feedback. I edited the function to account for non-Textarea FieldTypes. Should I report the issue regarding the PageTable Refresh as a bug? The markupValue-hook is definitely not called.

This is a great solution, thanks! My ready.php hook: $wire->addHookAfter('Fieldtype::markupValue', function($event) { $page = $event->arguments(0); $field = $event->arguments(1); if($field->type == 'FieldtypeTextareaLanguage' or $field->type == 'FieldtypeTextarea') { $displayValue = strip_tags($page->get($field)); if(strlen($displayValue) > 100) { $displayValue = substr($displayValue,0,97).'...'; } } else { $displayValue = $page->get($field); } $event->return = $displayValue; }); Only problem I am seeing now: after the modal window to edit the pageTable fragment closes, the content refreshes and shows the full content again. The URL that requests the new content is this one: /processwire/page/edit/?id=1293&InputfieldPageTableField=content_elements&InputfieldPageTableAdd=1294&InputfieldPageTableSort=1294,1295,1296,1297,1298,129 Any idea how I can hook into the refresh? I will try the runtime property option too, just in case.

We are currently building a website that is going to use a lot of template fragments with the help of PageTable fields. The editor can build a page out of multiple fragments that will all combine to the full body content of the page. This works really really well. Here is a quick preview: Now, the problem we are seeing ist that not all template fragments are going to have a headline (see first element in the PageTable). This makes it in some cases difficult for editors to find the correct fragment to edit. So we tried to add the body content as a way to show more information. This lead to this: Unfortunately this makes the PageTable even harder to use if long texts are involved. Possible other solutions we considered: Make editors set a title for each fragment: they won’t like that and it adds a layer of difficulty Force them to add a headline and add a checkbox if it should not be displayed: additional complexity Add truncated text with stripped out markup to the column instead of the full text The last item on the list, truncating, is the solution we would prefer. As far as we can see that is not currently possible without extending the functionality. Does anyone have an idea how to best approach this? Is there perhaps a module that could help out? Functionality we overlooked? This is just a minor issue and we are more than satisfied with the incredible flexibility ProcessWire does allow. But we want to make life for our editors as easy as possible and this would help a lot to get us to that goal.