adrian

@Torsten - welcome to the forums. Firstly, PW no longer uses TinyMCE by default - it now uses CKEditor. Here is a post on how to set up RTL for CkEditor: Hope that helps.

Ah yes, sorry I didn't think to mention that - I think typically it's not something most users will want on the back-end, which is why it's only on the front-end by default.

Hi MichaPau and welcome to the forums. To change the password requirements go here: /setup/field/edit?id=3 You can access this via Setup > Fields, then under Filters, select built in fields and then edit the pass field. If you are running a recent version of PW 3 or 2.8 you will see these options: Back to your more general question, the ProcessWire Info panel of TracyDebugger (http://modules.processwire.com/modules/tracy-debugger/) will tell you the "Process" of the current page - see the "Process: ProcessUser" entry on the sixth row. That tells you that the User editing page is using the ProcessUser.module at /wire/modules/Process/ProcessUser/ProcessUser.module

Just occurred to me - this one is pretty obvious - by default Tracy is installed in "DETECT" mode which on the live publicly accessible server will automatically be detected as PRODUCTION mode which doesn't show the debug bar (unless you have the "Superuser Force Development Mode" setting checked. Tracy in production mode allows for logging and emailing of errors so it's still a useful tool, but a very different beast. I have actually been considering getting rid of the DETECT mode option - I think it is probably more confusing than anything - does anyone have any strong thoughts on this?

I think this is the same as: https://github.com/ryancramerdesign/ProcessWire/issues/1944 which should now be fixed.

Thanks - I am not seeing anything there that I think would be relevant, although I have never used TemplateEngineTwig. Would you mind testing Tracy on the same server without TemplateEngineTwig? Also perhaps try adding a redirect to a template on a fresh PW install - maybe there is some interaction with another module going on. Did you try switching to the other version of the Tracy core like I suggested - not sure which one you are one, but it might help to narrow things down.

Just to clarify - that setting is only relevant if you are using the SessionHandlerDB module. I am curious whether an update to the latest version of PW helps - there was an issue that was fixed in 3.0.25 that seems like it is related to issues with Tracy - I can't find the post easily right now, but I definitely think it is worth trying. Also, what about that Max Nesting Depth setting - did you change that at all? One final thing to confirm - am I correct in assuming that everything works as expected if those Object options are not enabled? If that's the case then I think we might be hitting some server session limit because they can be quite large, although just a guess at this point.

Use the dev branch of ImageExtra - it is supposed to be fixed there: https://github.com/justonestep/processwire-imageextra/issues/18

Please grab the latest version of Tracy before you do too much debugging.

@tpr and @bernhard - thanks for your thoughts on the Custom PHP panel - the form for submitting to gtmetrix is cool. I am happy to provide a place for sharing these snippets - let's see just how many get posted here for the moment and if we get a critical mass, then I'll either add them to the blog post, or start a Github repo. Let me take a better look at your Hook Recorder - it definitely sounds interesting!

Hi @Gazley, I am sorry this has been a painful debugging experience for you! I am trying to reproduce here without any luck. Are you running the Master version of the Tracy core, or the Legacy version? Does it help if you switch? Also, does the same problem occur with all custom panels removed? Use the Panel Selector Sticky option to quickly test without any panels enabled - if this helps, could you narrow it down to a specific panel for me? If none of that helps, could you send me all the code for your home.php file (and any other files that are included in it)?

@blynx - it just occurred to me - I think the problem may also be related to SessionHandlerDB - do you have that module installed? If so, there are two things possibly going on. The type of the data field in the sessions db table may still be text, but it needs to be mediumtext - Ryan fixed this here: https://github.com/ryancramerdesign/ProcessWire/commit/d4e8eb3dc54fbee54befa1ecc2d18b6269febc18#diff-cb9ec68dc3f620a40013310f547e904fR366 so if you upgrade your version of PW that will be fixed. Your MYSQL max_allowed_packet setting may be too small - you need to fix this one manually yourself Of course you can also just uninstall the SessionHandlerDB module as well, assuming I am correct that this is the problem

Does it make a difference if you only have one of those Object options enabled - trying to figure out if it's one in particular or whether it's the size of the content when more than one is checked. Also, did you make any changes to the Maximum Nesting Depth option? If that is too high, those Objects could get very large.

Second new panel today Introducing "Page Recorder" This panel records the ID of all pages added whenever it is enabled (so this is one you'll want off by default and just enabled via "Sticky" when you need it). This is perfect for all sorts of testing, whether you need to create a LOT of pages for performance testing or you are testing a form which is automatically creating pages. Once you are done with the testing session, simply click the "Trash Recorded Pages" button and they will all be moved to the Trash. Because pages are sent to the trash rather than completely deleted, I consider it safe to use, but I am a little worried that someone may leave it enabled when they are creating real content pages and then later trash them, then empty the trash without realizing it contains a page they want. If there is demand, I may consider adding checkboxes so you can remove certain pages from the list so they won't get trashed with all the others. Please let me know if you have any suggestions for functionality or the interface.

Is this any use to you? $_SERVER['SERVER_PORT'] It will return 8888 or 80 or whatever the port is.

<?=$config->urls->templates;?> would be a better solution. It is abstracting the path away to PW's config metadata which is generally a good thing in case there is ever a reason to change things. That is actually the same as: /site/templates/, so no need to prepend /site/ to make it work. Take a look at the options in the cheatsheet: http://cheatsheet.processwire.com/?filter=config->urls

I think it's a great idea - I have added to my list. In the meantime I have added a new "Custom PHP" panel which lets you return anything you want. which results in: Not very pretty looking I know - I am sure @tpr will have some style suggestions for me This is obviously not the best solution for things like page speed because it won't work with local dev sites, so as I said, I will work on dedicated panels for those, but this still may be helpful until then, and perhaps also for other things. Some other significant recent updates that I haven't mentioned. There are now separate default panel config options for frontend vs backend The User switcher now lets you logout (while maintaining the session and access to the Tracy debug bar). Until recently, you had to switch to a different user before the logout would work properly.

Have you tried? I honestly haven't played with images and the Markup module, but it would be worth seeing if you can, even if you need to parse it out from the enclosure yourself. I know it's old (and there are likely more modern solutions), but magpierss works with images.

Not sure - I haven't looked into it, but I based on this question, are you just generating the RSS feed so you can load it back into another site? If this is the case, maybe you should consider another strategy like making a simple REST service?

Try this version:

@Surikat - perhaps you are just trying to enlighten us all about RedCat and we appreciate that, but it does smell a little like advertising. You should know that ProcessWire is actually a framework first and the optional CMS component is actually built on top of this framework. I know this is not obvious from reading some of the blurbs on the website, but this is one of the main reasons why ProcessWire is so great because you have all the tools from the framework available for your use on the frontend, or to build your own CMS on top of it if you wish.

Can't you add it to the Character Replacements list in the Page Name config settings: /module/edit?name=InputfieldPageName

Just added color significance to PW and Tracy Log panel icons. Red for errors, exception, critical Orange for everything else, including warnings, info, debug, and any custom names PW logs Green for none All colors are based on log entries from the last 5 seconds which should cover everything loaded/redirected etc during the last page load. The idea being that you don't want the red or orange colors to be triggered from an error that was recorded days ago, even if it's the most recent entry. Hopefully this logic makes sense and it provides a useful visual cue to let you know that something was just logged. PS - as part of this I needed a different icon for the Tracy log panel - you'll see it's now burning campfire logs - it's actually hard to find a nice small icon for logs

Thanks again for all that. The one that stands out is the ToDo panel - I honestly haven't tested that on a large site with many template php/css/js files, so perhaps that is expected. Maybe I need to implement some caching so that it only scans files if they have been changed since the last scan. That should help with that significantly. Actually, you should take a look at the ToDo panel config settings and exclude any js/css from external libraries - I bet that is what is slowing that down. My ToDo panel renders in 0.03s compared to your 1.27s! I was actually thinking about adding caching to the Validator panel as well although that one will be a little more complex as it will require storing the rendered HTML so it can be compared. Regarding the generally slow nature of your local dev setup - have you read this thread: I feel like it might be the reason Tracy is running so slow - would be worth a look regardless as it seems like you are experiencing slow page loads even without Tracy, although of course I don't know what resources your page is loading.

You currently have this: Note that there is no "/" before "site", which means it will try to load: http://diofralealtrecoseparla.newageofcattolicesimo.it/site/templates/js/site/templates/css/style-wide.css instead of: http://diofralealtrecoseparla.newageofcattolicesimo.it/site/templates/css/style-wide.css PS Have a read here about urls: http://ifyoucodeittheywill.com/2009/03/absolute-relative-and-root-relative-urls/