Jump to content

szabesz

Members
 View Profile  See their activity

  • Posts

    2,927

  • Joined

  • Last visited

  • Days Won

    19

 Content Type 

Everything posted by szabesz

  1. szabesz
    Nice design! Thanks for the showcase. I find it a bit hard to navigate though. One opens a slide show at the bottom of the page (for example), but after closing it we are left at the top, so to check out all the photos one has to jump back and forth a lot, or am I missing something? And the /projects/sid-magazine/ slideshow starts with a different photo (different from the one we click on as a preview). At first I was confused. Another thing is Isotope: switching between ALL and COMMISSIONS swaps some(?) photos in the middle(?). I can only only see the top of three photos changing. What happens actually and why?
  2. szabesz
    +1 Since @rot does not seem to have enough time to work on his module (he can correct me anytime... ), I think it is quite reasonable for you to finish and maintain this module of yours. I would also be happy to use it, and share my findings about how it performs, etc.. meaning "testing it".
  3. szabesz
    Another option:
  4. szabesz
    Yes and no Maybe this time you could keep it a bit more organized like this 4 part tutorial: http://blog.mauriziobonani.com/processwire-basic-website-workflow-part-1/ as opposed to the journal style of this thread. If you take notes first and later on write the parts of a series one-by-one, then it can be more "tutorial like".
  5. szabesz
    +1
  6. szabesz
    This one? Looks nice to me If you were to write a separate tutorial as the development unfolds that would be cool.
  7. szabesz
    Thanks for the info @adrian! More thumbs-ups for valieand's request please: https://github.com/processwire/processwire-requests/issues/23 @ryan says: "Please note that we generally avoid adding features that aren't going to be used by at least 30% of the ProcessWire audience." Let's reach that 30% or even more!
  8. szabesz
    It is at least possible to use the forum to learn from others, but not practical and rather hard to do it on IRC. Forum content is searchable and somewhat organized, while IRC is not. The latter is good for what you normally use it for. Forum is a usable replacement for in-depth docs and/or books. I think this is what he meant. If so, I agree
  9. szabesz
    Hi, Something like this? More links to solutions: By Soma explained as an admin example: http://soma.urlich.ch/posts/custom-js-in-processwire-admin/ but works on frontend too, as long es we output in the head for dynamic variables https://processwire.com/talk/topic/8343-access-page-and-pages-variables-from-inside-a-javascript-file/#entry80823
  10. szabesz
    I see. Then the answer is yes. The "skeleton" of the markup is in _main.php, just like in the case of "site-default" profile.
  11. szabesz
    Well, I'm not sure what you are referring to by "main.php", but Ryan's blog post can be understood by looking at the "site-default" profile. You might want take a close look at it. There is a _main.php file used by this profile, the whole article should be viewed in this context.
  12. szabesz
    Quote: "Let's say that I'm using a _main.php file that serves as my primary document markup, like used in our current default site profile. It contains the main document markup, like this:" Ryan normally calls it _main.php (see: $config->appendTemplateFile = '_main.php') and this is where the skeleton of the HTML goes. This skeleton is extended and changed by writing code in the template files assigned to public pages, such as home.php. Otherwise you got it right I think.
  13. szabesz
    While I generally agree with @Beluga's reply, it should be mentioned that it is hard to control the conversation of a chat room regarding what sort of topics can be discussed there. So I do understand @Doug G's concerns, especially as @Pete mentions: "...or get help in a hurry if someone's there."
  14. szabesz
    Hi @EyeDentify I think you got it totally right, at least this is also my understanding of it. EDIT: I missed this one: "...full" HTML markup in the home.php" This "full" markup is supposed to be in "_main.php", but I suppose it was just a mistake that you referred to "home.php".
  15. szabesz
    How about this?
  16. szabesz
    Sure But this is the easiest Anyway, other options are in the thread we linked to.
  17. szabesz
    Hiding them by CSS (display: none)?
  18. szabesz
    Hi, is it the same question? If so, just read the topic. Edit: @kongondo beat me
  19. szabesz
    Hi Kongondo, I'm interested, although I have not used PadLoper yet, I might want to use it when time comes to get rid of any of "my Woo shops". Not in the near future though.
  20. szabesz
    LostKobrakai did not mention MVC at all, probably he did not even refer to it , as far as I can see. Speaking of MVC, I'm not convinced that "strict MVC" is that much useful either, and I'm not alone eg.: http://paul-m-jones.com/archives/6288 But either way, I do agree with @Robin S that lots of brochure websites do not need MCV or the alike, and even webshops can be successful without them especially if one does not have to refactor too much in it the future for some reason. When a system is based on solid system design (meaning the site does what the client needs in the first place) then there is less to worry about regaring possible refactoring. But it is getting off-topic here...
  21. szabesz
    Hello @darkmesaia I often recommend these to start with: Important concepts: https://www.smashingmagazine.com/2016/07/the-aesthetic-of-non-opinionated-content-management-a-beginners-guide-to-processwire/ Understanding Processwire Templates, Fields and Pages: https://medium.com/@clsource/understanding-processwire-templates-fields-and-pages-201aecd0a1a4#.m9yquavll Step-by-step guide, 4 part tutorial: http://blog.mauriziobonani.com/processwire-basic-website-workflow-part-1/ Approaches to categorising site content:
  22. szabesz
    https://processwire.com/blog/posts/processwire-3.0.49-introduces-a-new-template-file-strategy/#Comment12849 By Ryan: "What's described in this post is not a template engine, and not even related to a template engine. Actually it should work quite nicely alongside a template engine if you are using one. What markup regions do is essentially the same thing that the existing PW region() function does, but with some added flexibility and simplicity." If it can be used together with a template engine, then it is the way to go I think. While teaching to fish instead of simply feeding is good a concept, when there are so many different ways to fish, you have to start teaching by using one method only so that all the newcomers can learn the same thing at least at the beginning. This new method/strategy reminds me of Magento, but it is a lot simpler to implement. I do support it. Let's teach people (ourselves to begin with) how to use it with and without a template engine
  23. szabesz
    Hi, a related dscussion:
  24. szabesz
    Does this work on PW 3.0 though? One part says: It should. See: https://github.com/processwire/processwire-issues/issues/75
  25. szabesz
    By Ryan: "... the $config->userAuthSalt (which appears at the bottom of your /site/config.php file). That particular value is generated randomly when you first install ProcessWire. It is forever tied to the passwords as a secondary salt. It's not technically necessary to have it, and passwords are already blowfish'd, but I've always felt better having one part of the salt disconnected from the database itself. If that salt changes or is lost, then all the passwords are forever broken."
×
×
  • Create New...