adrian

Thanks @bernhard for the access to that testing server - very helpful! @blynx and @Gazley - does the latest version solve your problems? If it doesn't, chances are that you have SessionHandlerDB installed. You can either uninstall it, or edit your php.ini file and if output_buffering is set to 0, please change it to 4096. I am hoping to get a fix from the core Tracy developers so that neither of these changes are needed, but for the moment I think it should solve things.

HI @charger - isn't that the desired behavior? If it didn't create the pages that belong to the Page Table then you wouldn't be migrating all the content. Maybe I am misunderstanding though?

Hi @deltavik and welcome to the forums. Perhaps this module might suit your needs: http://modules.processwire.com/modules/inputfield-chosen-select/ There is another similar one, but it escapes me at the moment.

Sorry I think I must not be understanding the scenario you are seeing - any chance on sending through a screenshot or two highlighting what you are seeing and how you think it should be different. Unfortunately I haven't been able to figure out how to make template file variables available in the Console panel - I have tried a couple of times without success, but it is definitely on my list to revisit because it is definitely a significant limitation at the moment. I can get them (like I do in the Variables panel), but can't persist them, but it's still on my list of things to do, so I will be taking another look at it. Thanks - I don't suppose you'd be willing to make a list of those places where it's incorrect for me?

Thanks for mentioning those issues with the Variables panel. The latest version deals with this in a better manner - let me know your thoughts on the new behavior. Some other changes in this/recent versions. You can now use bd() in the Console Panel You can now trigger the Mail, Page Recorder, and Event Interceptor panels from the Console Panel - really nice for testing your mailing / page creation code from the console The PW and Tracy log panels are now included in the AJAX debug bar

If I understand correctly, the Mail panel in Tracy should be what you are looking for. It intercepts all wireMail() calls and shows the results in the panel instead of actually sending the emails. Oops - sorry about repeating the content of @szabesz's post - I replied without reading through all the replies which were on the next page.

Thanks for the report - that was introduced only a couple of versions ago. I think it should be fixed in the latest version - please test and let me know.

In addition to @horst's comments, in case you don't know, you can find out which php.ini file is being used from phpinfo() - if you have Tracy installed, turn on the PHP Info panel. Otherwise you can get this info from php -i|more in your terminal. Sorry if this is already basic knowledge for you!

A series (currently 10 episodes) of video tutorials in German by Leonid Lezner https://www.youtube.com/channel/UCwkKKtIeOzfIqF8X5gNP0_g

Haven't you already solved this

Glad that helped @Torsten17 I am not someone who deals with multilanguage, but your suggestion sounds good to me, although I would have thought you'd want a double underscore to make the "dir" translatable? It might be best to make this suggestion in a Github issue so it gets Ryan's attention.

@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.