tpr

In the latest v0.5.5 there's a new optionchecked filter. I usually have a tough time when I have to check whether a Select options field has a given option checked/selected, so this filter is about simplify this. I've decided to use a "dot notation" because it makes things easier to read imo. The filter accepts the id, value and title too: // 3=show_header|Show header {if ($page|optionchecked:'page_options.3')} ... {/if} {if ($page|optionchecked:'page_options.show_header')} ... {/if} {if ($page|optionchecked:'page_options.Show header')} ... {/if}

Same here, if someone tells the recommended format for version numbering I'll stick to that in my modules.

Thanks, it was a .text() vs .html() issue, module updated 1.7.0.

Thanks, I like it. Perhaps the template link attracts the attention too much, I would go with something like this - but of course I can live with the current one too

The attached version of TD doesn't offer anything extra compared to the built-in admin search so I don't regard it too useful - of course on the frontend side it could be handy. In this case it would be great having a non-panel version of it, only a small input line in the TD bar, with results appearing above it, growing upwards. Probably this is harder to implement, just an idea. See the attached image how I imagined the ajax-loaded page title (plus the template name used). It should be one line only, cropped if too long, with a small font size. Also its placeholder space should be there all the time to avoid jumping when typing.

No, it's minimal design at its finest I like the site btw (webGL'd here :))

I haven't try this feature so far but the first idea that came to me was to have some kind of info about the page even without clicking on the buttons. How about an ajax loaded line showing the page title as you type, in the bottom of the panel? I think that would make the panel more versatile but of course it's only a nice-to-have kind of request

There are tons of tutorials and other staff to learn Laravel. If you keep the PHP way I do recommend digging into that. You'll learn many useful stuff (MVC, OOP, templating, Composer, etc) and it's also relatively easy to grasp. Plus knowing Laravel nowadays for a PHP dev is a must imo. And once you know Laravel, all other frameworks will be much easier to understand. I agree that if there's no project to start using a new tool can be frustrating. I usually decide what to learn and during the learning process a project usually comes to my mind that could be created/rewritten in it, or at least more fun.

troll feeding on Yes, we are fanboys because PW is a system that can be loved. We enjoy what it has to offer and since you are here I guess Django is not like that. troll feeding off

If at least one language is inactive, then list all and strike through the inactive ones. My other idea is to show this language list in a tooltip somehow.

I've managed to solve the uikit issues mentioned by @jmartsch, will be available in the next update. I'm experimenting with a feature called "language indicators", which would come handy to see the active/inactive languages in the page list: The idea is to make it visible only if not all languages are active, otherwise list all languages (abbreviated to the first 3 chars of their titles). Inactive languages are marked with a line-through. I think it's the quite talkative at first sight, and doesn't mess up the page list if you have many languages. Thoughts?

Sorry, that's my fault, I've mixed the string vs numeric versioning and that's why the chaos (adrian reminded me). Next time I'll double check

Thanks, now I have a slight clue what's going on

Great topic idea. FYI, in AdminOnSteroids you can globally add plugins (with buttons, if available) to all ckeditors. Please feel free to suggest a plugin to add to aos. Additionally you can selectively set, add or remove buttons per user role, template, etc with its FieldOverrides submodule.

IUC in action:

Thanks, that could work as a workaround. I guess I would actually solve it differently but using the same idea (specifying fields manually).

@jmartsch Are you sure it's the long-click module setting that causes that? I can't reproduce it using PW 3.0.84 and the uikit theme that comes with it. @Macrura Could you share? As I remember there were no CSS class on those inputs that I could use to distinguish URL fields.

I'm using it on a few production site (well, everywhere almost :)) and one of my friend too tried it and kinda liked it. Even though I don't feel it's production-ready, I've made many changes during its lifetime so a code cleanup would be necessary. It's currently more admin-oriented, mainly to support multi-language in emails and messages, but everything can be overwritten by code. Adding fields are strictly available via code though. I can add it to github and write some docs to it (currently there's none).

While at it, perhaps a new folder too?

Do you have a field with html5 validation that prevents the Save action to perform? Aos triggers the Save button so this is what I can think of. I have modified this feature a few weeks ago to trigger Save instead Publish when creating a new page but I don't think this is the culprit. I needed to modify things under the hood to take the DOM order into account, to find the Save btn first on new page. I guess I can show the save overlay for a second and then remove.

No, that tells that you always need to add sort=sort to ensure the admin sort order. I've used sort=sort in aos but noticed that custom sort order needs additional work. You can check it by adding a custom sort order to the parent page, and then see how the prev-next link targets are out of sync.

If you have an own server you can upload images there and link to them. I sometimes do this, which also has the benefit that I can modify images easily if I need to, and they will remain there whatever happens to the forum.

Yes, as it takes the custom sort order into account, that you can set in the Children tab of the parent page. By default it falls back to"sort".

I've noticed that I need to set the sort order to keep the admin page order (this is what users expect I guess). You can do this like so: $query = 'include=all, sort=' . $this->editedPage->parent->sortfield . ', parent='.$this->editedPage->parent;

Thanks, I like these kind of bug endings