Jump to content

szabesz

Members
  • Posts

    2,634
  • Joined

  • Last visited

  • Days Won

    16

Everything posted by szabesz

  1. Thanks for the info! I cannot answer that but a search engine that does not even list processwire.com on the first page is weird: https://yep.com/web?q=ProcessWire for this query, I get "processwire.com/blog/posts/pw-login-for-facebook/ " as the 19th item in the search result list, and that is the closest thing to finding "processwire.com". Sure, "github.com/processwire/processwire" on the top of the list but still...
  2. This one looks cool: https://www.autohaus-bendel.at/fahrzeuge/300862-citroen-citroen-xm/ Nice site, BTW!
  3. Part two with "Adding in relevant 3rd party or Pro modules" would certainly help newcomers as well, in addition to "Optimizing settings in /site/config.php".
  4. Like caniuse.com but for PHP, eg: https://caniphp.com/?s=null It is possible to support the project: https://ko-fi.com/magicroundabout https://github.com/rosswintle/can-i-php Happy coding! :)
  5. +1 I am working on my first Unpoly driven frontend and loving it so far. With so little code one can do a lot! What I'm aiming at the most is this: no businness data validation / calculation / transformation / whatsoever on the frontend, only in PHP at server side! A lot of "hidden" features are lurking in the Unpoly docs, reveling that things can be quickly implemented by applying a few HTML attributes only, see for example "dependent selects": https://unpoly.com/input-up-switch Unpoly is what Bootstrap is for CSS but for JavaScript, so to speak.... This is an important remark, I think. What they solve (including Unpoly) is not exactly that, but one can code all the "businness data manipulation" on the server only, and use these JavaScript libraries to implement an app like behavior in the browser relatively easily (especially in the case of Unpoly). One still needs to find the "right" backend framework/CMS/CMF that fits ones need and implement the HTML rendering for the frontend as required by the chosen JavaScript framework.
  6. Thank you for asking! Actually, I sometimes mix up the terminology of "nested repeaters" and "depth repeaters" by accident, or just simply forget about "nested repeaters" which I have not yet used. I need it for "depth repeaters" as that is the one which allows for free drag and drop, but for the user being totally free can be a drawback, just like in the case of a "page builder" setup. It is surely strange that no one has reported it before, but people seem to be trying/doing it differently, please see: https://github.com/processwire/processwire-requests/issues/440 https://processwire.com/talk/topic/27073-colours-in-repeater-matrix-items/#comment-223553 Maybe it is me who is trying to use this feature in a way in which it should not be used, I do not know: And the above results in the color value being seen as you can see in the screenshot I provided in the GitHub issue linked above, but it is also seen next to the fa-arrows icon of the InputfieldHeader.
  7. @fruid I'm sorry for providing only small bits of help only but you can also consider using URL hooks instead of putting both "normal page rendering" and AJAX responses into the same template file. See: https://processwire.com/blog/posts/pw-3.0.173/ In one way it is cleaner and more flexible than putting both responses into the very same file, but of course, you have to "manage" the two different responses in different files in this way. Another way of separating AJAX request/responses from the page request is to use URL segments, but with URL hooks available since PW 3.0.173, I would not use that technique anymore.
  8. What about the "X-Requested-With: XMLHttpRequest" header? The $config->ajax call requires that to be sent.
  9. Worth noting: https://processwire.com/blog/posts/processwire-2.6.8-brings-new-version-of-reno-admin-theme-and-more/#new-this-gt-halt-method-for-use-in-template-files quote: "Now you can call return $this->halt(); from within any template file, and it will prevent further output from that template file (and anything that comes after it, like an appendTemplateFile). This enables output to stop, but PW's normal execution and shutdown process to proceed normally. Please note that return $this->halt(); must be called from directly within the template file, outside of any function or class scope."
  10. While we are at it, I am particularly interested in possible Repeater Matrix features that were mentioned or just partially implemented: 22 October 2021 Blog post: "...the ability to control what item types are allowed where, kind of like the Family settings on page templates." 3 December 2021 Blog post: "...specify a background color for RepeaterMatrix item labels with a hex color code in your repeater matrix item labels." Currently, getting the label of a matrix item results in the added the hex value being revealed to the user, which means that even in the admin the user sees things like "block one #FF0000", "block two #FFFF00", etc... I think Repeater Matrix should trim the color value form the end, so that this feature can actually be used. The "Family like settings" would be especially useful for "page builder" like use-cases, but I do need it for a "product configurator" I am currently working on, where various properties of a product can be defined by organizing Repeater Matrix items. The only problem with such a setup is that currently the user can create configurations which do not make sense. I could "validate" what the user has done upon saving the page and spit out some admin message to inform the user what the issues are with what she has done, but it would be better to prevent her from messing things up in the first place, by applying "Family like settings" to repeater items.
  11. For those who do no have access to the Pro fields support forum, Ryan expains a similar issue like this: "One thing about repeaters is that they sometimes have extra pages in them called "ready pages", which are basically abandoned new items that are saved for the next time you need to add an item to the repeater. So in your loop that iterates the repeater items, you'll want to check that the items are published and/or not hidden before considering them valid for your calculations. if($child->isUnpublished() || $child->isHidden()) continue." see: https://processwire.com/talk/topic/24967-hook-says-there-are-twice-as-much-repeater-items/?do=findComment&comment=210451
  12. Thank you for this quick report, Ryan! Have a great weekend, everyone! Why not 3.1 for that matter? Are there any particular requirements that qualify for 3.1, BTW?
  13. Hi @adrian Have a great vacation and take care! I see. I will probably ask for help at the Unpoly repo first to figure out more and next ask the Nette devs as you suggested. Thanks!
  14. Hello Adrian, I am working on my very first Unpoly 2 driven frontend and found that either Tracy's or Unpoly's JavaScript break in some cases. I get errors in the console like this: Uncaught TypeError: this.elem is null Panel http://mydomain.test/products/?_tracy_bar=js&v=2.9.1&XDEBUG_SESSION_STOP=1:29 loadAjax http://mydomain.test/products/?_tracy_bar=js&v=2.9.1&XDEBUG_SESSION_STOP=1:444 loadAjax http://mydomain.test/products/?_tracy_bar=js&v=2.9.1&XDEBUG_SESSION_STOP=1:442 <anonymous> http://mydomain.test/products/?_tracy_bar=content-ajax.5de8b397b6_2&XDEBUG_SESSION_STOP=1&v=0.44454897717264863:1 The above example starts happening when I first use the browser's back feature. I tried to relocate unpoly.js to body's end from the head but to no avail. Either Unpoly breaks or Tracy's JS, depending on the loading order. Note, that Unpoly recommends using its own event handling methods: https://unpoly.com/up.compiler as its automated event handling might interfere with "random JavaScript", as we probably see in this example. Are you willing to deal with this issue? If so, what else should I do to help you make them work together? Thanks in advance,
  15. Sorry, I fixed the URL above which was a wrong one. This is the one I was referring to: https://github.com/processwire/processwire-requests/issues/230
  16. It might be a good idea to somehow persuade more PW devs to give more thumbs-ups this request: https://github.com/processwire/processwire-requests/issues/230 Anyone reading this and supporting the request, if you have not yet clicked the thumbs-up icon, please do it now :) Me too, of course. However, the most important reason why I have not yet looked at Bernhard's modules in details is that he keeps rewriting them every now and then (which is quite understandable but still...) and I certainly have no time to keep up with all the changes. Most importantly, I stick to ProcessWire and to some other (pro/non-pro) modules because I rarely have to deal with any breaking changes throughout the years. That is why I am dreaming of Ryan picking up this request one day in the future.
  17. Hello, I've never used it but I casually read the posts of this LoginRegister module during the days, and as far as I can remember, this module has its own issues but still usable even from a security standpoint. However, I highly recommend that you carefully read most of the topics before deciding whether to use it or not: https://www.google.hu/search?q="LoginRegister"+site%3Aprocesswire.com%2Ftalk Personally, next time I need frontend user login, I will use the commercial version instead. EDIT: to make it clear, I was referring to Ryan's free/commecial Login and Registration modules, so I added a google search URL to show what I meant.
  18. Me to. Just recently I've read two PRO module forum posts where the PRO modules did not work properly with lazyLoading enabled. I am surprised that Ryan enabled it by default, as usually he does the opposite, like in the case of Markup Regions, Page Classes and Functions API. Why should useLazyLoading be en exception to this? Now I need to add $config->useLazyLoading = false; to all the configs of all "my" sites to be on the safe side.
  19. I do not think that a naming convention that fits all needs exits. Still, I mostly find useful using these "rules": "Thinking in reverse", something like French, where adjectives/describing words are usually placed after the noun: text_head, text_subhead, text_body When using date/time: it is yyyy_MM_dd-HH_mm_ss or similar what I use. The important thing here is the order, so when alphabetically listed we also get chronological order. I try to avoid sequential numbering (text_1, text_2, etc) as they are meaningless. Adjectives/describing words should be semantic, whereby a name of something indicates its intention, purpose or relation to other objects and not its properties which might change: text_h1 instead of text_bigred, for example When dealing with composit "objects/things" I often stick to the basic idea of BEM but I am not following it strictly. If lots of multiple of the same fields are needed for a template, I simply pick the most appropriate looking Pro field(s). I know this does not help those who do not have them, but if a project is big enough to warrant for such needs then the Pro fields are probably worth it, especially a DEV license is not that expensive at all, I think.
  20. Me too :) That's why I wrote this "cheat sheet" for myself and shared it just in case others find it useful too: https://processwire.com/talk/topic/23641-markup-regions-pw-vs-data-pw-different-behavior/#comment-201538
  21. Hello Camilo, Nice to see you still blogging about PW. I like your post a lot, however maybe the "Requires some learning" bit is too vague. Yes, you explain it right afterwards but changing it to "At least basic PHP knowledge is required" or something similar would make it clear right out of the box. I think there is at least one more important bit to explain in more detail: frontend possibilities. "....way of code organization, neither force you to learn a new template engine." Sure, but it is an advantage that there are modules supporting template engines for those who need them or one can integrate any of them relatively easily. Also, the core provides Markup Reagons for those who prefer plain php templating for the output rendering, which makes life easier too. I would mention and point/link to these options as well, not just the JSON "alternatives". Again, nice blog post for sure.
  22. Ok, I've tested it, deprecated is colored green, looks great. I just do not know what to ask the Nette devs for. My limited knowledge of Tracy Debugger is restricted to Adrian's module, which is configurable extensively while core Tarcy does not seem to be configurable at all: https://tracy.nette.org/en/guide However, the idea is that Adrian's module should provide settings for separating "low level of importance" and "high level of importance" (what should these be called, btw?). So what should be the feature request to the Nette devs in the first place?
  23. I will first check what Adrian shared, next, I will gather my thoughts and share them with you guys so that I can present something convincing...
  24. Yes, that was the issue. Some time ago I added some a template code based "sort url" logic to the home page using URL segments, so that was it when the RSS feed stopped working. Now I am wondering how else I should go about implementing "short urls", something like this: example.com/xyz-promotion Do you think that I can use this https://github.com/apeisa/ProcessRedirects/releases for such a thing? I've never seen/used this module before, that's why I'm asking.
  25. Wait, this might be the issue, I go and check it....
×
×
  • Create New...