Jump to content

szabesz

Members
  • Posts

    2,838
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by szabesz

  1. @Speed I have MAMP Pro so I do not know if it works (also, it is an old post) but you might want to give it a try: http://jonathanmh.com/using-virtual-hosts-with-mamp-free/
  2. Welcome to the forums @tiefenb! more about urlSegments: https://processwire.com/docs/tutorials/how-to-use-url-segments/ https://processwire.com/api/ref/input/url-segment/ Have fun with ProcessWire
  3. I haven't yet used the module, but I'm sure sooner or later I will, so I thought I should I share what I think about this part of your question. Personally as the developer/superuser I need the possibility to edit anything that generally does not break the site. Since this is not such a feature, I think only non-superusers should be restricted, but even this restriction could be optionally disabled by the superuser, at least for a given user role specified by the dev/superuser. Lots of small sites use at least three user role/group levels: Superuser-Editor-Guest where superuser is often the developer itself, and editor is the client. At least, this is the case with most of my sites. My clients do not want to touch things that might break the site, so they ask me to "hide" those settings.
  4. I have just checked in Safari 9.1.1 and it is like your screenshot. It might be a CSS/JS compatibility issue, some sort of edge-case situation that might be hard to track down, I suppose. Anyway, after I update the viewport by resizing it, the background pops into place.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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
  14. 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
  15. 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.
  16. 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
  17. So you have updated the API docs, thanks! How about a cross link to the blog entry too?
  18. 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.
  19. I can prove that he does so: He even writes tutorials about the topic: http://soma.urlich.ch/posts/custom-js-in-processwire-admin/
  20. Don't we have a Moderator around? @horst is speaking alien language which is seriously off-topic
  21. 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.
×
×
  • Create New...