Jump to content

szabesz

Members
  • Posts

    2,838
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by szabesz

  1. "could I target search by default to a specific template ?" The only issue with it in this particular usecase (if I get it right) is that we get a dropdown select in the case of filtering for templates, we cannot use free text based search.
  2. Hi bernhard, I get it now. I wasn't thinking about developing for giant organizations where various people the dev has never heard of might post notes in this issue tracker. I've never worked for/in such an environment, but now I see why you might need it. I also understand what you meant by "this page | this template | this website" As for "somehow connecting the error log entries with client notes" idea, I also think it would be great to have something like that. It might also be possible to automate it based on the "time stamp" of the log entries and the "time stamp" of the Notes, by showing those side-by-side which happened about the same time. What if the client generated a lot of log entries? Showing the most suspicious ones might help too. But this might be an overkill, especially when things are normally running smoothly
  3. It's quite understandable that you want to stick to it, we like it too. It might be possible to separate the two modules (TD and "Notes") by introducing a third one that handles the panels and on which the two other modules depend, but it is extra work and probably not worth the effort, because we have "enabling/disabling tools quickly as needed" features already, so why bother dealing with separate modules when they are tightly integrated anyway? The only reason to do it is to introduce a "Tracy Debugger panels" like API into the core, so that other developers can rely on it. That way Horst's ALIF (Admin Links In Frontend) module, Tracy and this so called "Notes" could live under the same hood. I was also bold enough to think about somehow integrating/merging the GUI of not just these "three" modules mentioned above, but also the new GUI of the core Debug Mode Tools. However, so far I could not come up with a reasonable proposal since Debug Mode Tools has quite a different approach, while TD and ALIF are very similar in GUI terms.
  4. Hi, 1. Is PW 3.x compatible with PHP 7? I"m not yet using PHP7, however ProcessWire 3.x runs on it and I've been reading reports in the forum to confirm it. But watch out for modules you might have that might have trouble running on it, e.g.: https://processwire.com/talk/topic/9507-php-7-coming-soon/ 2. Would you recommend PW 3.0.18+ in production? E.g. is it too "dev" or already "prd"?) Probably it also depends on the modules you use, such as anything not compatible with the new ImageField module: https://processwire.com/blog/posts/major-images-field-upgrade/ 3. Any known PW-related issues with migration from myisam to innodb? Here is the related blog entry: https://processwire.com/blog/posts/pw-3.0.15/ Older post from Ryan: https://processwire.com/talk/topic/10287-database-scheme-includes-no-foreign-keys/#entry97876 4. Pros/cons of switching to nginx + mysql + php-fpm? (apart of lack of support, e.g. need to maintain config manually with each upgrade) Never used it, so I skip this one
  5. "name + email + phone on that panel? like "how can i help you?" We should only let authenticated clients (users) see this "Notes Panel" in the first place, shouldn't we? E.g. the developer sets up PW/Trace Debugger with a few users for people that might use it in the first place. From then on, there is no need for providing additional personal info. Only drawback is that they need to be able to login... but they will use the site anyway, so time to learn "something new" Filtering features are welcome, I think However, what do you mean by: "this page | this template | this website"? Another website? Aren't we working on the one in question already? Also, do we really need filter for page vs template? The client doesn't understand it, so they do not need it. Any usecase for us, devs? Priority: "high | medium | low" Personally I've never been able to use these. At first sight they look useful, but in reality these do not tell anything about desired deadlines. That is why I always use: asap, before launch, after launch, "nice to have in the future" or an actual deadline if any. Message types: "bug | request | comment" quite useful, I think.
  6. Thanks for sharing! (Just for the record: note that there are plenty of Bootstrap navigation related topics in the Forum https://www.google.hu/search?rls=en&q=site:processwire.com/talk+Bootstrap+navigation&ie=UTF-8&oe=UTF-8&gfe_rd=cr&ei=BUlEV_nTNNOv8wf4pKi4Ag )
  7. "...too lazy to use greenshot for screenshots..." I think this is the point! If they can just type their instructions ON the page itself where it belongs to, they do not have to make a screenshot. Sure, they still need to be able to express themselves clearly (they should at least try), but this way we know which page they are referring to (or at least part of it).
  8. I have already given up on them In my experience, only about 5-10% of them take the time to use such a tool (properly) anyway. I have a Word doc dedicated to this, with simple color coding. This is what they can/care to use. Very far from being perfect but at least something. The worst thing of using this "tool" is that my manual maintenance work is needed to keep it in a usable state. Currently I'm struggling with "time", but I'm interested so I will try my best to help. I also encourage others to join in the fun Many thanks, enjoy your vacation!
  9. I like the idea of turning this module into an issue tracker with debug support Jokes aside: If we could somehow list both php code TODOs and these Notes in an aggregated view, that would be great. When I cannot list all of them, those notes/todos are are kinda useless. Also, I always put my todo list in priority order, my todo items are even further organized into "categories" such as: asap, before launch, after launch, "nice to have in the future", etc... since an unorganized list is not too useful either. But the coolest thing would be to be able to indicate if a Note is only for the developer or for the client too. This way we could place Notes on the pages where they belong to, so that clients checking the site during development can instantly see what is done and what is still under construction, so they do not start reporting bugs, typos, missing elements, etc... in the first place. It could save a lot of time (fewer and shorter discussion/emails exchanged). Better yet, what if clients could also take Notes, I mean open issues belonging to that page? Ok, I stop it here, this is too much already...
  10. I must admin I never read this thread properly, I just loosely followed it, but I thought it might be of some sort of help: https://processwire.com/talk/topic/12151-wire-queue-basic-implementation-of-simple-queues/
  11. Sure, the Tile, thanx for correcting me. Using my numbering of the levels described above, if we have level1-level2-level3 open and click on level1's Title, then level2-level3 "disappears", so even the direct children are closed up. If you have the same subtree open and click on Home (level0), the direct children of Home do not close up, only level2-level3. You need to click on Home once more to have a completely closed three. Maybe it is intentional, since a completely closed three might not be that useful after all.
  12. Thanks for the explanation! Sure, the built in module installer works fine. The idea behind using your module is to search for modules. The module directory's search on processwire.com works, but your module provides additional ways to fiter the directory which I like a lot. The best thing would be to implement similar features for modules.processwire.com I suppose.
  13. Well, the current implementation seems to be inconsistent. Let's say Home is level0 and I have a tree form level0 to level3. When I have level3 open, by clicking on Home level3 and level2 are closed up, level1 remains open. Levels should be closed either: level-by-level , I mean stepwise, as ottogal pointed out above: e.g. by clicking on the Name Title the complete subtree: e.g. by clicking on an icon between Name and the number of usage count Edit: Title vs Name
  14. Besides, it's more like a hack than a solution, anyway
  15. In addition to this, I also recommend reading up about the very basics of Object Oriented Programming, http://www.tutorialspoint.com/php/php_object_oriented.htm at least the concepts behind it. Although in the case of ProcessWire frontend development you are not "forced" to implement anything in OOP, knowing the fundamentals helps a lot to understand the API and its usage. An often used technique in the OOP world is method chaining. You do not have to use it, but when you want to look up someone else's code, you need to how and why it works: http://www.xpertdeveloper.com/2010/09/method-chaining-in-php/ BTW I highly recommend bookmarking http://www.tutorialspoint.com/php/ You can use this method before you jump into your trial-and-error experiment: Whenever you start working on something unfamiliar, say sending emails, study some basics in pure PHP, say: http://www.tutorialspoint.com/php/php_sending_emails.htm After that, look for alternatives in the ProcessWire world: API support, module support Of course, it is recommended to use the API and/or modules whenever you can, but understanding why is so makes working with them easier. Hope this helps, good luck, and never give up!
  16. The UI of the two panels should match as much as possible, otherwise I'm quite happy with anything that works with the fewest clicks possible, and provides ways to easily see in which states the settings are Oh, and many thanks for the new panel! Now I just need to train my memory not to forget about all the goodies your wonderful module offers
  17. Hello Sephiroth, If you do not feel uncomfortable just by installing WordPress, I recommend cloning this one: Alo EasyMail Newsletter: http://www.eventualo.net/blog/wp-alo-easymail-newsletter-guide/ A few important points to consider: - emails should be sent in "small" batches, to avoid being blacklisted quickly - the possibility to test the newsletter with a small set of test email addresses is a must Sure, tons of other features are needed, that is why I pointed to this WP plugin, which works well.
  18. Hi suntrop, Have you already seen this tutorial? It already has tree parts and introduces Template Engine Factory with Twig: http://blog.mauriziobonani.com/processwire-basic-website-workflow-part-1/
  19. Thanks netcarver! Since you recommend it, does it mean that it just works fine in ProcessWire 3.x too? I can imagine that it does not implement anything fancy that might be deprecated, but I have never used it so I thought I ask before wasting some time on it
  20. Just to highlight some recent additions to our toolbox – from ProcessWire 3.0.13 and up – we can construct our selectors by using arrays too: https://processwire.com/blog/posts/processwire-3.0.13-selector-upgrades-and-new-form-builder-version/#selector-engine-array-support
  21. Welcome, ProcessWireLearner, Check out the link of my recent post: https://processwire.com/talk/topic/2985-how-to-create-a-simple-news-system-for-pw/?p=120314 in the Wiki, especially this page: http://wiki.processwire.com/index.php/Pages_Overview and the "long tutorials" tagged pages: http://wiki.processwire.com/index.php/Category:Long_Tutorials but still, probably the most recent tutorial is this: http://blog.mauriziobonani.com/processwire-basic-website-workflow-part-1/ This is not strictly on data relationships, but should give you a head start on understanding the concept of using Pages for all your relationship needs
  22. You might also want to consider adapting one of these methods: Probably good for experimental purposes too: https://processwire.com/talk/topic/9638-different-templates-folder-for-different-usersroles/ Best for replacing (e.g. based on some sort for conditions) complete "front end themes": http://processwire-recipes.com/recipes/use-different-sets-of-template-files/ And we also have Adrian's Tracy Debugger which supports "hacking" the compiler cache of ProcessWire 3.x for temporay testing purposes. But this is probably not what you need in this case, I just mentiond it for the record. EDIT: "typo"
  23. I was about to ask it! Thanks a lot!
  24. Thanks trp, fixed the typo As for the accordion: I'm missing the instant access of the second level of the main menu. Besides, positioning the mouse cursor over the little flash icon is troublesome, so I just tend to click the menu anyway. EDIT: second level
×
×
  • Create New...