szabesz

This one and a permanent disable feature is what I'm voting for. I mean the "System Info", since this is the one that cannot be turned off. "Disable Once" and "Disable Permanently" would do, I suppose.

Hi, Probably the simplest way to do this is to implement a simple import script, such as this one: Yeah, I know it's XML, but CSV should be simple too, eg: http://stackoverflow.com/questions/9139202/how-to-parse-a-csv-file-using-php Hope this helps.

@Zeka How about unchecking "Frontend" in "Debug Bar and Panels > Show Debug Bar"?

"Valitron is a simple, minimal and elegant stand-alone validation library with NO dependencies." That's the way I like it Thanks for the detailed instructions. I will probably use it in one of my projects in the near future.

As opposed to AOS, we can enable Tracy for both frontend and admin, so the disable feature would be nice to have on its main panel too, which I have already missed a few times.

Hello, Which one is the module in question? Module related questions should normally be asked in their own forum section. Anyway, don't you have a backup by any chance? The sort of problems you describe can be fixed most easily be reverting to a backed up version which you should always create right before trying out new modules or any other mayor changes to you site.

Wow, that's cool and quite useful too. Thanks for educating us!

Great showcase indeed! http://www.memelpower.com/en/technologies/ Does that mean that you are shifting emphasis from ModX to ProcessWire?

Impressive However, since you do not use checkboxes, there is no way to perform a batch operation (at least I cannot see it in the screengrab). Is this intentional?

Thanks Can! We might want to add: "This method does not need output formatting to be turned off first, so make sure that whatever value(s) you set are not formatted values.", which is not the case with languages but worth mentioning nonetheless: https://processwire.com/api/ref/page/set-and-save/

Current behavior can be confusing (at least I tripped over it), see: This is the proposed behavior:

Oh my! I figured it out... Currently I use: $config->templateCompile = false; but the block only shows up when $config->templateCompile = true; I should not be surprised, but maybe the block itself should not disappear, but a simple message could be displayed reminding us to enable the compiler in the code in the first place...

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