Jump to content

szabesz

Members
 View Profile  See their activity

  • Posts

    2,951

  • Joined

  • Last visited

  • Days Won

    20

 Content Type 

Everything posted by szabesz

  1. szabesz
    I did not. How can one do that? ? Anyways, I have just figured out what the issue might have been: my workflow is that I install modules on the production site, configure it and afterwards clone the db and sync files to my local environment. However, I did not clone the AutoTemplateStubs folder from production to local because the cache folder is excluded in that case too. So storing AutoTemplateStubs in /site/assets/cache makes it a pain for me to use the module ?
  2. szabesz
    At first I set the prefix to "stub_" and no(!) AutoTemplateStubs folder was created at all. Afterwards I uninstalled the module and installed it again. This time I left the prefix at the default "tpl_" setting and now I have the AutoTemplateStubs with the php files in it. So now it works. However, AutoTemplateStubs being in the cache folder, I cannot set the whole cache folder to be excluded, which I have been setting so far so I do not accidentally start editing a template cache file, for example. I do a lot of global search so excluding the cache folder is a must. Can't you make it optional where the AutoTemplateStubs folder is created? EDIT: actually I usually mark /site/assets folder to be excluded, not just /site/assets/cache
  3. szabesz
    Thanks for sharing the module @Robin S I have just installed it and followed the instructions but it does not appear to do anything. What sould I do to troubleshoot? I'm on a Mac using PhpStorm.
  4. szabesz
    I would never call these "discussion boards" a forum though. I am glad we have a proper forum and not something like these.
  5. szabesz

    State of JS 2016

    szabesz replied to adrian's topic in Dev Talk

    https://2019.stateofjs.com/ TL;DR summary: https://www.i-programmer.info/news/167-javascript/13360-javascript-still-popular-.html "So we can see that the use of React (which is the most used technology in the survey with 16,099 users) has increased while it popularity has been pretty steady while Angular's popularity reduced as its adoption grew and over the last year people became more even negative towards it." My comment on this is that it looks like Vue.js is the second most popular frontend one these days. ""JavaScript is moving in the right direction" with over 80% agreeing and only 4% disagreeing. So all is well in the land of JavaScript."
  6. szabesz
    I think it is ok to ask Ryan in the ProFields/RepeaterMatrix forum.
  7. szabesz
    It's hard to tell. PageTable is in the core and does not get any attention so it's been in its initial state ever since its introduction. Table received some extra features during the years and Ryan has plans to improve it.
  8. szabesz
    Are you referring to Vanilla Forums? Looks like it is being maintained and in constant development: https://open.vanillaforums.com/categories/blog https://success.vanillaforums.com/kb/docs
  9. szabesz
    Thanks! However, to make the thread readable, could you please put the code in a "spoiler"?
  10. szabesz
    Hello, this module might help to achieve that:
  11. szabesz
    What if – in the future – Ryan decides to implement a core module with the same name? We thank you! ?
  12. szabesz
    What keeps me trying out Wireframe is the lack of templating support, so I would welcome this addition for sure. Currently, I do not use any templating engine for PHP so I cannot recommend based on experience, but would like to raise my points of view on this: Twig 3.x: needs at least PHP 7.2.0 to run Blade: PHP >= 7.1.3 Latte: v2.5 requires PHP 7.1 (supports 7.4). v2.4 requires PHP 5.4 (supports 7.4 too). What I prefer is not being forced to update PHP too often. In this regard Latte looks like a good choice. Another factor is how solid the development community behind the library is. I would never use something like a "one man show Blade offspring", as even though one can rely on the parent project for years to come, what happens when the developer of the offspring abandons his project? The reason I am still sticking to plain php for templating is that it needs no updating nor maintenance, which is a timesaver in the long run. Regarding others: https://www.dunebook.com/best-php-template-engine/ BTW, have you taken a look at utilizing Markup Regions somehow?
  13. szabesz
    These ones popped into my mind: AnyImagePicker GlobalPickerForImages GlobalImagePicker GlobalImages GlobalImageSource PickAnyPicture PicturePicker And some creative ones too: ImagineGlobally ImageOutsorcerer (not misspelled but intentional ? ) ImageSorcerer ImageOutsourcing
  14. szabesz
    I'm no expert but to me it looks like for sites not enduring transaction heavy traffic MyIsam is still a bit faster, eg: http://kedar.nitty-witty.com/blog/choosing-between-myisam-and-innodb-mysql-storage-engines also, corrupted tables are less problematic, eg: https://www.knownhost.com/wiki/developmental/mysql-myisam-innodb Anyways, thanks for all refactoring efforts!
  15. szabesz
    Ooops. I have no site using InnoDB and I am not planning to use it. So no ImagePicker module for me I guess ?
  16. szabesz
    Thank you! It makes a great Christmas present for the community! I haven't had time to do further testings but I will surely try out the new module during this holiday season.
  17. szabesz
    BTW, when can we expect that to happen? Sounds like sooner than the end of December maybe? Is it going to be the first production ready version? Thanks for sharing all your hard work, and do not forget to ship it with a "Donation button".
  18. szabesz
    +1 ?
  19. szabesz
    +1 As for the config being confusing / overwhelming, it could be solved via step-by-step guides in the readme file, especially if it has screenshots to showcase all three setups.
  20. szabesz
    @kongondo If you have some time, could you please look into the issue I have? Please see above. Thanks in advance!
  21. szabesz
    Sounds good to me.
  22. szabesz
    Thanks, I have updated the module, and set up two image fields for the Home's template. Afterwards, I created an "Image Reference From Another Page" inputfield, however, in "Chose a page to get images from" any page is selectable except for Home. Any idea why is that so?
  23. szabesz
    Let's put the current state of the module to some "stress test" first for some time. After that, I happy to support "multiple images" request ? I'm gonna upgrade, thanks!
  24. szabesz
    Sure I could, however normally I use the template of the home for site-wide settings, which is a simple but working solution. The home page is rarely edited by my clients so in this sense it is a perfect fit for rarely edited site-wide settings or – in this use-case – as storage for such images. Thank you in advance! I'm going to wait for that, I'm not in a hurry.
  25. szabesz
    Thanks for your work and sharing the module, much appreciated! I have just installed it, but stopped at this stage as my current use-case is: I would like to use it as a "page header" image picker. What I would like to do is this (at least theoretically): I want to add two image fields to the template of the Home page . One for "header image normal", and another one for "header image tall". So the home should be used for storing these site-wide images. 'Image Reference From Another Page' should be either added to the home template itself and to all of the templates of top level pages, so that the user can pick one image to be used as the header of that page. However, because I use Home as the source of images, I do not want the module to search for images under its child pages. I guess the above outlined setup should be ok, but before spending time on trying it out, could you please confirm that it is a working setup or not?
×
×
  • Create New...