szabesz

Strange issue, indeed! It seems to be ok in my Chrome though. However, it is such a "strange desing", that it is hard to tell whether what I see is intentional or not. At least the backgoung and the footer look ok.

I'm asking out of curiosity; did you also try Chrome's "Empty Cache and Hard Reload" feature? e.g.: http://www.thewindowsclub.com/empty-cache-hard-reload-chrome I found that Chrome often needs it in similar situations to yours.

I did not remember correctly... This line and its comment changed form RewriteRule "(^|/)\." - [F] to RewriteRule "(^|/)\.(?!well-known)" - [F] but still, "probable change" is always reported anyway.

One more thing to add: I did see an actually change to .htaccess a few weeks ago, but it was just some changes in some comments if I remember correctly, so no actual change in the way things work. However, this was a change, so it should be considered as such. But it does not really matter as long as "probable changes" are always reported for some reason.

It's a lot of code to dig through, so I do not have the time to analyze it but one thing I noticed is that I found values like these: class ProcessWire: const indexVersion = 300; // required version for index.php file (represented by PROCESSWIRE define) const htaccessVersion = 300; .htaccess: # START PROCESSWIRE HTACCESS DIRECTIVES # @version 3.0 # @indexVersion 300 index.php * @version 3.0 * * Index Versions * ============== * 300 Moved much of this file to a ProcessWire::buildConfig() method. None of these can be used to compare against the actual version. What am I missing? Anyway, the change detection does not work as it was probably intended to work ot it is useless in its current state. I just use a diff tool to see what actual changes there are, if any. If only version numbers are compared to each other, then the message of the module should not suggest that it has actually detected "possible changes". I can be mistaken, but this is what I have gathered so far.

Normally I upgrade by using the ProcessWireUpgrade module and I've noticed that 3.0.30 is the one that shows up as the latest version. Is that intentional? I've been having another issue with ProcessWireUpgrade and it is about index.php and .htaccess changes detection. It keeps detecting changes even when there are no changes at all. I've been using a diff tool to check for differences and usually there is none, but the module always reports changes.

How about any 3rd party modules that might "interfere" with the session handling? I know it is a vague idea, but if you have 30+ sites, you can try to compare them to each other in order to figure out what might cause the culprit.

Thumb's up! I'm not a GitHub guru, but it sounds like a clever idea. To tell the truth, I'm a 3.x only guy, but following your blogposts, I can see that you really take it seriously, and thank you for this! I've seen awful major version changes of other CMS'es/frameworks already, so I'm sure anything you will finally come up with will be far better than those.

I was thinking of this too. It is incredible what you have achived so far. You might want to charge for the module in the future. How about a light and a pro version? But psst! It wasn't me who gave you the idea

Ok, thanks, I get it. I'm with you This topic is bit too advanced for me anyway, I was just trying to figure out how to handle this... So a big praise to @tpr for the idea, and to you too, of course

Variables in single quotes are not evaluated to their values, rather, they are treated as strings. You have to use double quotes to do that. However, @matjazp is right, you do not need any of them is this case, because the url is already a string.

I have just looked up the forum to learn more about Advanced Mode, which is recommended to be turned off, so for folks like me this new panel is not really something I might ever use if one can easily run into unwanted situations (which might easily happen without a deeper understanding of ProcessWire, at least that is what I have gathered). Something like @tpr suggested above could be a lot more helpful, being a safer alternative to this current approach. I mean, I can see that this panel can be useful too sometimes, but for folks like me (who is not a hard core ProcessWire developer), it seems to be out of reach, so to speak. Thanks for the panel anyway! Even if it's not for me, I have at least learnt a few things about ProcessWire's Advanced Mode

So you have updated the API docs, thanks! How about a cross link to the blog entry too?

Thanks Adrian for the new panel! This one sounds "scary". At least, a real pita situation can emerge out of the blue, so I was wondering if we could be somehow warned about potential issues. At least a general note, but in case of known issues (such as this ProcessWireUpgradeCheck) it should be somehow marked, or even removed from the list if it is no use disabling it. One more thing I've been thinking of it recently but this new panel has reminded me to mention it: There are so many panels already that it would be nice to have some sort of short description of them in the module's Settings. Maybe the simple (asm)select is not the one that fits the bill anymore, but something else that supports accompanying labels/tooltips. This addition would be especially great for newcomers.

I can prove that he does so: He even writes tutorials about the topic: http://soma.urlich.ch/posts/custom-js-in-processwire-admin/

Don't we have a Moderator around? @horst is speaking alien language which is seriously off-topic

In addition to @Martijn Geerts's piece of advice, you might also need something like this: https://www.yourhowto.net/strip-spaces-string-php/ It's not really about find, but about working with strings.

This is the first time I've heard of this browser. Looks awesome and luckily based on Chromium! (I got used to its dev tools and I'm sort of lost when using other browsers' dev tools.) Thanks for the tip!

Tell me about it - sometimes they try to simplify to the point of losing functionality! I have just turned this default behavior off. I do not know why I haven't done so earlier. As for the other issues: thanks for striving for perfection. We are in the same boat

I have changed it, and it does not make a difference. I mean I always get 150 characters, even if I set it to something else. Another issue it the column content of the string. On this page it gets really wide (last colum can hardly be seen): And thanks to Apple's decision to hide scrollbars by default, I often do not even notice that a window's content can be scrolled. That is my own grief, however, I just wanted to mention that on a Mac it can be even more confusing when the table is cut off right before the last column.

If you enable it by default, you might want to remove the the core version altogether, so there will be no confusion at all. We have something more advanced, no need for the plain version, I suppose.

@adrian "Could you PM me the html from that panel": I can, however, how about installing https://github.com/NinjasCL/pw-ghost by @clsource ? This is what I'm refactoring to my needs currently. My version is still very similar to his, so you can use it for testing. "collapsed sections": fiddling with collapsing is slow, I think simple links are more efficient. "$authors" is never used (it is in the original profile too, I have not yet removed it) I do not know if the detection fails or not sometimes, I have not yet spent too much time checking the results of it. "collapse/expand all toggle": sorry for my confusing words. I was talking about one toggle button to collapse/expand all at once. Initially all of them are closed, right? I do not seem to remember... "You can set the length of the string in the config settings though (default is 150) - does that help?": more or less. It is informative to see 150. I will experiment with it. I'm just trying to save space somehow "...turning columns on/off - does the width of the panel matter that much...": the width. We have nearly reached the width of my Air's screen/viewport (1440px). By turning on/off I actually meant hide/unhide.

Hi @adrian The Template Resources panel has started to grow fast, so I thought just before it outgrows my notebook's screen, I present a couple of suggestions: Returns and Class columns can be merged. After all, the info "Object" is redundant. Long string like a body's HTML code takes up a lot of space in the Value Column. Can you introduce AJAX only loading of such values? Or it can be made collapsable just like arrays/objects. That way initially the column would be narrow when arrays and objects are not expanded. It would be nice to have a "collapse/expand all toggle" for arrays/objects. What if columns can be turned on/off? At least the "Files/Lines" column. It could initially be in its closed state. This is what is used the least, I suppose. BTW, how about highlighting variables used in one template only and only once? It can help us spot variables no longer used or the developer might want to eliminate such variables by using expressions instead. How about jump links at the top to sections of the panel (to variables, constants, functions, included files)? The first two lines could be merged into one paragraph (These are all the... If you are looking...) to save some more space. "Panel generated in 183.67 ms Panel content size: 1.1 MB" could also be merged into one line and could be placed at the top, so no need to scroll down... Hope you find these suggestions useful. The following is just a screenshot to show what it currently looks like on my machine.

It is worth mentioning that the developer ( @kongondo ) is away for a while, see: Also, note this quote: "A MarkupDynamicSelects for use in the frontend is planned if there is enough demand for it.". You can find it in the intro post. And people have already started demanding it

Does anybody really like infinite scrolling? I mean it looks fancy, but from the usability point of view infinite scrolling is horrible. Just try to find an image on a looooong page of thumbnail listing after you passed it half a minute ago.