szabesz

Thanks @Robin S, that is what I was afraid of... is it just me who is missing this block in PW 3.0.32 and 3.0.33? This is my screenshot: (note: I have a ProcessWire site running on 3.0.28 where this block does show up, and I used to set this option for the site where it is gone from)

We could also set these up in the admin on a template-by-template bases. Now its also gone. Something smells fishy.. Sure, in theory FileCompiler=0 would allow for more control.

I see. Well, I just wanted to test: "Setup > Templates > your-template. Click the Advanced tab, and choose "No" or "Auto" for the "Use Compiled File?" vs $config->templateCompile = false/true; But the former is missing in ProcessWire 3.0.33 devns (BTW, it used to be under the Files tab, not Advanced in 3.0.28 and 3.0.30 at least)! Does anyone know what happened to this setting? I used to set all of them to No (disables compiler), so that $config->templateCompile = false/true; can be used globally, and that was what I was about to suggest, but I cannot test it, 'cos the admin setting is gone...

"C:/inetpub/wwwroot/pf/site/assets/cache/FileCompiler/C:/PHP/adodb5/" ? Does not look like a valid path. Anyway, why not include __DIR__ . '/adodb.inc.php'; ?

https://processwire.com/blog/posts/processwire-3.0.14-updates-file-compiler-fields-and-more/#file-compiler-updates https://processwire.com/blog/posts/composer-google-calendars-and-processwire/#processwire-and-composer https://processwire.com/blog/posts/happy-new-year-heres-a-roadmap-for-processwire-in-2016/ "Composer support. While we already have partial composer support in the current devns branch, we still have more work to do in this area before we start documenting and highlighting it." https://processwire.com/blog/posts/multi-instance-pw3/ "PW3 isn't yet up on Packagist, but will be after it's in master release." Hope this helps.

So true

http://modules.processwire.com/modules/process-hanna-code/ Using Hanna Code from the API If you want to populate Hanna Code from the API, you can do so using the render() method, like this: $hanna = $modules->get('TextformatterHannaCode'); $page->body = $hanna->render($page->body); We can just provide the hanna code itself, if we want to, just as you do it in your example. BTW, are you sure you have never seen this in the docs?

I'm glad you could finally make it work. Actually, I'm not really experienced in setting up virtual hosts, that is why I use MAMP Pro in the first place. However, if it works for you, why spend money on something you do not need ?

We cannot see the backend, however if it is just as clean and easy to use as the frontend's graphic design, then it must be really well crafted! A big applause to the creators! PS: I noticed a missing image: https://www.niinuagilitysport.fi/virallinen-agilityharjoitus-09-2016-viikkorata/nutrolin_acana_orijen/

How about Hanna Code?

We are OT here, but anyway, the pull request was based on this (if you take a closer look, you can see): https://community.letsencrypt.org/t/drupals-defualt-htaccess-file-breaks-webroot-authentication/3014

Probably you did not update the file, so you need to apply this manually: https://github.com/ryancramerdesign/ProcessWire/commit/2c3c3abde48e870a50198ce55ab0195694562a0d

Yes and no Actually, in the case of the site in question Let's Encrypt is not used. The rule has been updated recently, and I simply noticed it: https://github.com/ryancramerdesign/ProcessWire/pull/1751

@Dakrtom I definitely do not want to scare you away from the Forum, but I do not think the Google's (or a similar) translator will be enough to communicate. Don't you have other options?

I can send you my site in question. It is something I will use as the base of all my future PW sites and it will probably be released as a site profile too (which is still a long way away, though...). So, do you need it?

Except that it ruins the Reno header completely

This one works!

Hello @marvinbible, welcome to to the forums, If I understand you correctly, you are looking for the way to install a frontend theme, in the sense of installing WordPress, Joomla, etc... themes, right? In the ProcessWire world there is no such thing at all, so there is no way to install it either. We have "site profiles" to choose from during the installation process of the system. There are various ways to apply various template files to a given page of the site, but normally you cannot just switch themes to change the look of the frontend. This is because – as opposed to WordPress –, there is no "official way" of building frontends. ProcessWire gives total freedom in this area, there is no core support for theming the frontend. We also have Admin Themes, which can be switched though. This is what is somewhat similar to WordPress frontend theme switching (and it is based on the concept of modules, actually), but it is for the admin area, not the frontend.

@Ivan Gretsky If I understand you correctly, you are looking for a way to build (as easily as possible, of course...) a "basic", stripped down admin area, as opposed to trying to apply restrictions to the built in one, right? Without knowing too much about PW's inner workings, I do not think it is something that is supported by the core as such, otherwise we should have already found hints on such features. That is why @renobird is talking about "Are you looking to create a sub-set of the admin and restrict particular users to just those pages?", I suppose.

My mistake again... I was in haste in the morning, so... actually, the class AdminThemeDefault is added to <body> and not <html>.

Oh, sorry for that Well, switching theme I have AdminThemeDefault, but sticky header does not work for me either. That's "AdminTweaks -> Sticky header", right? Since installing AOS, I do not use the default theme anymore...

I've just updated to 0.5.6, and I do get the AdminThemeReno class and the sticky header.

If we probably do not get too many log entries, then log to file will probably do, however, if we do get too much stuff, logging is normally recommended during testing sessions only.

I often see such features to be (superuser) configurable: no log, log to screen, log to file, log to both.

This discussion might help: https://processwire.com/talk/topic/13977-custom-php-code-selector/?do=findComment&comment=125688