tpr

Thanks, works like charm! As for the names I trust your experience Anyway, such names (descriptions?) wouldn't do so much harm to the UI.

I tried to use "|" in the selector but didn't worked: [[template=tutor|event,name={pagename}]] Result: domain.com/[[template=tutor%7Cevent,name=...]] Using only "tutor" or "event" works fine though. Is this a bug or is this not supported? (v1.5) Plus a question to v2: will it have a feature to add a name to each jumplink? That would make it easier to see what the jumplink does, e.g "Redirect old events to page Events". They would be even searchable using the browser search feature or with filterbox feature of AdminOnSteroids.

Great - now you could target using ".InputfieldRepeater[data-min="1"][data-max="1"]" in your CSS. Be aware that you will need to set display: none, and also remove the padding on .InputfieldContent too. In this regard a hook would be better to add skipLabel (and setting field->label="" as skipLabel works only this case afaik) with PHP.

If there's a CSS class that identifies that it's a one item only field then you can easily hide with CSS (eg admin.css with aos).

Never thought that the "Always show pagelist actions" could be beneficial to me but I was wrong. While setting editor access, it is handy to see whether they are able to add new pages to a page or not, without needing to hover the pagelist item. Btw, here's a trick I use to simplify setting up roles. I use the same "basic-page" template for several pages, and some of them may have children, some not. But you can't set it page level, only at template level. What I do is create a new template "basic-page-nochildren" and set it's fieldgroup to "basic-page" (need to set $config->advanced to see this feature on the template edit page). Then assign these templates to pages that shouldn't have children, and because of the same fieldgroup, they will also have the same fields as "basic-page". Update: don't forget to make the template "basic-page-nochildren" viewable by creating a template file for it, or set the "Alternate Template Filename" to "basic-page" on "basic-page-nochildren" template (Files tab)

Still wasn't perfect - "images.field.label" worked only for Image fields but not for other. However I figured out that this one actually works (for a Date field named "date_created"): {fieldgroup.date_created.label} It still returns the label int he default language, but with the %lang_id% it's outputted fine: {fieldgroup.date_created.label%lang_id%}

Got it working by adding a token %LANG_ID% - will be included in the next update. {images.field.label%LANG_ID%}

Yesterday I was not completely happy with the pagelistmarkup feature because occassionally I need to output dates and as I store them unformatted (unix timestamp) I can't output them formatted in the page list. Now I have added a feature to set the formatting using the following syntax (borrowed from Latte template engine): ({date}|date:%Y. %B %d.) As you can see it's very flexible, the only issue remained is setting the locale. My idea is to leave this thing to the developer and do not add it here (maybe a hook?). Of course this issue only affects multilanguage sites where you would need to output month names in different languages too, but using only number format is OK.

Indeed. Hardcoding the language ID works (images.field.label1017) but the substitution by PW runs before I could replace the ID.

Could you show your code and module settings?

Sorry, this tweak is only a regex preg_replace, nothing more. But this one works - kudos to Tracy Debugger letting me find this out {images.field.label}: {images.count}

v108 is up, containing a new feature to add markup to pagelist items: It uses the [tag.class][/tag] syntax, making it flexible to use. The module also contains default styling for the "em" tag (which is the recommended): {title} [em.company][b]{company_ref.title}[/b][/em] [em][i]images: {images.count}[/i][/em] Output in the pagelist:

Definitely better - I would also recommend looking into the heredoc syntax.

Try with $config->paths, files are not accessed via url.

I have no time to investigate further but this fixes it (line 344) // if ($image->pagefiles === $pagefiles) { if ($image->pagefiles->page->id === $pagefiles->page->id) { Perhaps "===" is the culprit? PHP docs says

I was about to make (some) fuels optional but haven't noticed performance issues having all enabled. Editing the module is not a smart option, I can add a hook instead to modify the fuels to be loaded, if there's a need.

v2.4 is up: added additional filters and macros (optional, see README) added 'languages', 'fields', 'templates', 'logs' to the default API variables (suggested by Pixrael) remove cache directory on uninstall

I was hoping the opposite Not sure what's going on here.

Just upgraded to PW 3.043 dev and getCrop() doesn't seem to work (returns NULL). Downgraded to 3.042 and no issues. I've downloaded a fresh copy of both PW versions so 3.043 should contain Ryan's fix too. Anyone having the same issue?

Well you could hide with CSS add a CSS animation to unhide after a few seconds, which would ensure the select to be visible (in theory). Because of the few seconds delay the JavaScript will probably make changes to the DOM so the original select won't be visible. I've used this tecnhique in a site with a loader, to remove the loader even if there's something with JavaScript. Anyway, I think this kind of FOUC doesn't matter too much in an admin.

Also, are the pages in question active? Check the Active? checkbox on page Settings tab next to page names. Plus are access rights set for those pages, or do they reside under the Admin page?

Great, thanks There's a funky calculation going on when setting the columns so I decided not to risk things with multiple aos_column_break fields

There's a way without additional colbreak fields, see the readme. I didn't want to flood the admin with extra fields.

It this project online to try? Perhaps it could be solved by CSS only.

I don't have any particular feature in mind now but I'm sure there will be one later