tpr

Sure, I can add workarounds, just wanted to share these, thanks.

I get an 500 error after the third failed login attempt: Please wait at least 10 seconds before attempting another login. (in /wire/modules/Session/SessionLoginThrottle/SessionLoginThrottle.module line 97) SessionLoginThrotte settings are the default ones, 5 sec and 60 sec, no IP throttle. I'll disable the SLT module for now but I'm curious whether this happens for others too. Using PW 3.0.100 and PageProtector 2.0.4, but just checked on another site running on 3.0.52 / 0.2.1 and it happens there too.

A feature request for the future: allow login only with a password. As a workaround I used a simple str_replace and added hardcoded "value=USERNAME" attribute to the username input, plus a good old display: none to it. This way it doesn't show up but contains the username pre-filled. The same could be perhaps achieved if there was a per-page setting where we could enter one username. Then the module could add a hidden input with an encrypted username (instead of a text type username input). But maybe you have a better idea. I needed this because the client needed a password protected page without asking for a username. Fortunately the protection doesn't need to be bulletproof so my workaround is fine for now, but in the future it would be nice having this built-in.

Try adding title template.name in a template's Advanced tab, under "List of fields to display in the admin Page List. Not sure if it works with 2.7.2.

Sure, it's fine to me having this somewhere low on your todo list

No, I haven't tried this time but recently I've added buttons to it. Just wanted to mention this because this feature could be useful also to others (or am I the only one blessed with such a client? :))

Hi @adrian, what do you think of adding a Facebook Sharing Debugger panel to the module? It requires login and there's no GET way to force "Scrape again" (as I know) but still it would make easier to check the opengraph data on a page. For me a simple link would suffice (unlike the Validator panel).

Check FEEL, see my sig.

Thanks for the remainder @Robin S. I've replaced the character icon with an SVG. I've committed the changes, no version bump. Perhaps I would have used FontAwesome if it would have been possible to set it as a background-image but that's not the case. I've tried adding the SVG variant of the FA search icon but then searched for a slimmer one. There are only a few icons in AOS and I wouldn't like to increase the overall module size.

I've added the new sticky pagelist action, @theo's langswitcher fix, Tracy panel z-index fix (hopefully) and other minor fixes in v1.9.1. I noticed that I was using one SCSS mixin too many times (for icon-only pagelist actions) and it contained rules that I could apply to items outside the mixin. After cleaning this up the final CSS shrinked from 127 to 93 Kb so it was worth the trouble. I removed the js lib "perfect scrollbar" that was used to replace the browser scrollbar with a mini one (RenoTweaks). From now on AOS uses CSS to achieve the same thing, and is available in Chrome only (you can find it under Misc). It's a sacrifice but results in much leaner code, is controlled by the browser so it's unlikely to break, and modifies every scrollbar in the admin. For example they are available in Tracy panels too and also in CKEditors (the latter required additional efforts though): Documentation is in progress, as usual

I've added a new filter called replacesubs that allows adding placeholders in format ((name)) to fields, and then use an array or a textarea content to fill them with values. You can apply it to a field content and all available placeholders will be replaced. Unlike getlines you can add new placeholders and data sources at any time, no need to touch the code. Plus you / your client can add HTML and formatting to them in the CKEditor.

Thanks @adrian, and in AOS there's also a "Add Trash action also for non-SuperUsers" feature that might come handy.

I would probably just override the CSS on these fieldsets (by loading a CSS file to the admin).

Is anyone interested in the sticky implementation shown two posts above? I think it's a simple but reliable implementation that can be handy not only in the admin but on frontend too.

@theo Thanks - does it help if you change "get" to "findOne"? I'm experimenting with a new sticky pagelist action, loosely based on the ProcessPageListMultipleSorting module. The idea is to create a global "sticky" field and hook into ProcessPageList::find to prepend sort=-sticky to the original selector (keeping template and page level sort intact). This way un-stickying a page will restore the original sort order. When sticky-ing a page it finds the sibling with the highest sticky value and sets it to an even greater value, so it will go to the top. It works fine so far, the minor glitch is that if you would like to move eg the second to topmost sticky page to top you'll need to unstuck first and then re-sticky (or edit the sticky field value manally). I find the idea to add extra move up/down sticky actions an overkill. The order also can be queried on the frontend because the new sticky field is a real field.

Nice find, thanks. I've changed to an arbitrary cookie but couldn't get any errors though. Could you try wrapping the lin in question with this and see if the problem goes away? if ($this->wire('pages')->get('template=language,id=' . $lang_id)) { $this->wire('user')->language = $lang_id; }

I noticed that in Firefox 59 using link href "#" and scroll-behavior: smooth didn't scroll up smoothly. I've added an id "top" to a top-level div and changed the href to "#top" so now it works as it should. Does anyone have some background info on this, or perhaps it's a bug? In earlier FF it worked fine if I remember right. Btw I also had to tweak the CSS because in FF the scrolltop link appeared below the fold if the page was smaller than the viewport.

Perhaps a hook priority issue? Search the forum, eg here: https://processwire.com/talk/topic/1983-prioritising-hooks-for-same-event/

There are lot more elements in Reno, including the sidebar and many header elements. Setting #wrap { z-index: 0 } also solves the panel issue but still the panels are above menus.

I haven't found a way to make all the z-indexes work nicely together. I could add #tracy-debug { z-index: 100000; } or so when sticky headers are enabled in AOS but that would make menu dropdowns and such overlapped by Tracy panels.

I've adjusted the CSS so now the scrolltop link doesn't extend the page height if the page has small amount of content. That is, if there is not enough content to scroll the scrrolltop link doesn't show up and the page doesn't get any vertical scrollbar. In older browsers the scrolltop link shows up fixed even in this case but that's a minor thing imo. I've updated the example to have content toggle button so it's easy to see.

Likewise IE/Edge is for downloading a browser, WP.com is for spreading the word about the best CMSes ?

That also means I don't need to install LibreOffice but use it within PW on localhost? Cool! ?

I will not be too popular with this but looking at the example above I won't be happy if I would inherit a project with such code. I have dealt with some unusual template syntax recently and from a team and maintainability POV the best is to stick with tools that most developers know, or is understandable at first sight. Of course it's only my thought but I always felt markup regions is a dead end. There are already lot of tools/languages to learn, why add another one to the stack that you can't use anywhere else? (and when there are many alternatives)

I see now, but I think the & in the selector would be misleading. As for the array syntax I can say nothing as I haven't used it so far.