szabesz

Hi, did you search the forum? This is a question the comes up quite often: https://www.google.hu/search?q="it+appears+to+be+forged"+site%3Aprocesswire.com%2Ftalk&ie=utf-8&oe=utf-8

Maybe there is some confusion here. There is a topic discussing it:

Er, well - maybe, but only the stable branch

If it does not take off then why not? However if it does, I do not even want to be nearby... I do NOT trust software as I've already seen some in operation

Thank you! I've been missing it

This should be the keyword here. Also meaning a related API dedicated to support custom configuration options as well. No one likes to reinvent the wheel I guess, so some sort of "sub-theming" or better yet transportable settings and customizations would be nice to have instead of two or more completely separate admin themes.

How many admin themes are we going to have? This is not clear to me. We can expect UIkit 3, that's great However – just as I stated above – I'm a bit concerned about seeing people working on different admin themes instead of joining forces... I might be misunderstanding something here, I dunno.

May I ask why? The readme says: "Obtain a fresh copy of ProcessWire 3.0.51 or newer"

Sure! But the "main feature" of AOS is that is has on/off settings for each feature it implements. Anyway, I find it hard to see that having "three or four" admin themes around is better than a single but configurable one. You suggest modules to modify the admin theme by module developers, but which one when there are more than one? @tpr had to put some extra work into his module just to support the current two. Will he has time to support even more? Or anyone else, for that matter? Why not dedicate our time to only one, but a configurable admin theme, rather than spitting out "a lot", trying to customize them via modules later on? I might be wrong here, but this is how I see it at the moment.

Ryan says in his new blog post: "For instance, if you like a 2-column layout (like Reno) rather than 1-column layout (like Default) then that's a simple matter with the built in grid system. Nothing is set in stone, and our focus is on establishing the system to provide the path and flexibility for it all." also: "So what I've been doing here is coming up with a basic admin theme profile that the skilled designers in our community can then run with. My hope is this will be a collaboration where we'll come up with the best admin themes anyone has ever seen for any CMS. As a community, we'll want to select one or two that we can also bundle with the core in ProcessWire 3.1 as well." Well, +1 for a sidebar, but even better to have a setting that moves the menu from the top navbar to the sidebar and vice versa

That is why I wrote the above. Some instructions are very important all the time, some (lots...) can be hidden though when no longer needed. @tpr had to "hack" a lot of things just to realize a lot of features of AOS that will propaply break with the new theme. Generally true of course, however, most AOS users use most (and definitely not all) the features of the module, which boost productivity.

It might be obvious but I would like to point out that this would be the right time to implement most (if not all ) of the features of AdminOnSteroids which means at least a built in admin theme settings page to customize things to our liking, similar to AOS. However, there are features in AOS which can even be made better when implemented as integrated parts of the admin theme, such as "hiding"/revealing the Descriptions and Notes of fields. Having Descriptions and Notes around is extremely useful, but only in "development mode". When things are set up, they just take up space, distracting navigation and focusing, so I generally "hide" them by AOS (turning them into tooltips), but oftentimes I disable AOS, just to be able to skim through them quickly. Enabling/disabling AOS is not the best solution, because I loose all other functionalities of the module, but a native admin theme feature like this would only switch the relevant option of the admin, not all the others all at once. This can even be taken to the next level by being able to specify it on a field-by-field basis. The above mentioned example is just one, AdminOnSteroids is full of handy-dandy goodies that could boost the new admin theme a lot if implemented in an integrated manner.

Ok, Sorry, now I get what you wrote... I get the same behavior when changing the setting to "No", $page->httpUrl does return the trailing slash no matter what.

Hi, are you sure about this? I get the trailing slashes in both cases, just as the docs says: https://processwire.com/api/ref/page/url/ BTW, $page->url should return /about-us/ so your example implies something else must be going on, I guess.

Thanks to UIkit 3 being hookable, it is really easy to change the look of any componenets: https://getuikit.com/docs/less#use-hooks Even this is supported: "Should there be neither a variable nor a hook available, you can also create your own selector. ... This will sort your new selector to the right place of the compiled CSS file."

+1

Well, that depends... If you have a domain for the site or create a subdomain for the site, then we are talking about two different situations. For example in the case of a standard cPanel only account: say you have dev.example.com and want to install ProcessWire in /public_html/dev_example, in that case the default .htaccess file just does its job fine. However, when I moved the "main" site – which runs under the domain the cPanel account is tied to – to a subdirectory, only these rules did the trick for me: RewriteCond %{HTTP_HOST} ^(www.)?szabesz\.hu$ RewriteCond %{THE_REQUEST} \s/+szabesz_hu/(\S*)\s [NC] RewriteRule ^ /%1 [R=302,L,NE] Where szabesz.hu is my site, szabesz_hu is the subdirectory. I inserted this before the line RewriteCond %{REQUEST_FILENAME} !-f Also $config->urls->root = '/'; must probably be present in /site/config.php to get page()->url return the url segments without the subfolder being part of it, more on this: https://processwire.com/api/ref/page/url/ Nothing else I found in the forum or in the docs worked in my case. And there are other situations as well, but I just wanted to point out this one, since I had to google around to solve it. Your scenario can be different though, so you might want to provide some information about what you exactly want to solve .

Evening @tpr Is it just me who is missing text-decoration: line-through; from the page list (tree)? See: It was also missing at least in the previous version. I have a site with AOS 0.9.96 where unpublished pages are crossed out (I know it's way back in time...).

+1 And thanks a million, as always...

As long as one can define the color, it doesn't matter

+1 for this one. Personally I do not have any problems with the other issues @tpr mentioned, but having to move the mouse cursor back and forth is a little bit of a pita, although I uderstand that this way you just have one menu for both narrow and wide viewports, which looks ok, but far from being ideal regarding UX.

Me too! See: While I like this indicator, it is way too subtle, not to mention that often I have Tracy turned off for the backend.

Hi @Doc I've never done it with ProcessWire, but here are some topics: Huh, that's all for now

+1 Experienced developers should not have problem learning the basics of Composer, however, using the ProcessWireUpgrade module is easier and even site owners can use it out of the box, so generally I prefer relying on it instead of Composer. This is a module that should support ProcessWireUpgrade as well, I think.

I have already started to build upon the new site profile: http://szabesz.hu/ I replaced uikit.min.css and uikit.min.js with their currently up-to-date counterparts (3.0.0 beta 9, February 3, 2017) so it looks OK in IE and Edge too.