Jump to content

bernhard

Members
  • Content Count

    3,101
  • Joined

  • Last visited

  • Days Won

    91

Everything posted by bernhard

  1. Interesting. It looks exactly as if it was drawn using yEd ( https://www.yworks.com/yed-live/ or installable version for Windows) Regarding the Page Builder, as @elabx said, there's nothing plug and play at the moment. See https://www.google.com/search?q=site%3Aprocesswire.com+page+builder
  2. Hi @venkatesham, welcome to the forum, not sure, but I think it is this one: https://github.com/ryancramerdesign/skyscrapers2
  3. This could also solve my request of adding images directly to that page πŸ™‚
  4. Nextcloud could be an option: https://nextcloud.com/providers/
  5. Makes sense! I don't think it would be confusing, but I understand that you don't want to support this. It was just an idea πŸ™‚ Yeah, but at the moment the alien is the uikit icon, because all other icons in the pw admin come from the fontawesome library πŸ˜‰
  6. I'm not an UI/UX expert either πŸ˜‰ Maybe something like this (elements beside the main image smaller, icon in the shared images inputfield larger): That has nothing to do with the theme used. Fontawesome icons are included in all admin themes. It's just the old 4.7 version: https://fontawesome.com/v4.7.0/icons/
  7. Hi @gebeer just tested it and everything works great. Great work! Not sure if the edit link icon is the best solution regarding UI/UX. If a user wants to upload an image I'm not sure if the pencil on the right was the first they were looking for?! Besides that I have to say that I really like your module πŸ™‚ Two more things: 1) What do you think of using pw-panels instead of the modal? I really prefer panels over modals. It's very easy to use and you can easily test it on your own: 1) replace pw-modal class by pw-panel on your link 2) execute pwPanels.init(); in devtools console 3) click your edit link and it will open in a panel Only the ajax reload would have to be triggered on panel close instead of modal close. Maybe you could even make that configurable in your module πŸ™‚ 2) Would would be REALLY great would be an inputfield that can also store custom images on that page. Take a news section as an example (I have this usecase on several projects): The user wants to show a featured image for a news item... Currently my setup is that he has to upload it for every news item. The problem is, that he uses the very same image several times across several news items. Your module would make it possible that he uploads it only once. So far so great πŸ™‚ But what if he wanted to upload an image that is for sure only used on that very single news entry (eg an image of an event). Using your field he'd have to upload that image on the shared folder and it would "bloat" up the shared folder. It would be absolutely awesome if he was able to choose either a picture of the shared folder or a custom upload that is saved for that single page only. Technically this should not be a huge problem as the shared images have their own page to live and the custom image could be saved in the folder of the currently edited page. Thx πŸ™‚
  8. Not sure, but is this what you are looking for? https://processwire.com/api/ref/inputfield/wrap-attr/
  9. Hi @gebeer, nice module, thx for sharing! Just tested it and everything worked flawlessly. 2 suggestions for improvements: When no image is selected the gallery could be opened by default (I guess that is what one would like to do in that case: Choose an image) Maybe there could be a link to the page that holds the images so if one wanted to upload a new image they could just click the link, upload the image and save the page. If your inputfield updated its content after that process it would even be better, but not necessary in the first step, I think.
  10. Hi shogun, welcome to ProcessWire πŸ˜‰ imho that's totally up to you... It depend's solely on your preferences, other workflows, integrations, team members... I guess 1) would be easier in the beginning and 2) might make more sense after a while when you are more familiar with how pw works (and how you work with it). You can do a lot more than just inject some API magic into template files. For example you can do field rendering (https://processwire.com/blog/posts/processwire-3.0.7-expands-field-rendering-page-path-history-and-more/#field-rendering-with-template-files) or use Markup Regions (https://processwire.com/docs/front-end/output/markup-regions/) that open up a lot of possibilities but also make things more complicated in the beginning (if you are new to them).
  11. That should be enough. You just need to make sure that the server setup works, so I'd install a fresh copy of PW manually to see if that works. Then you create the db user on the new server, restore the db, copy your files and you should be up and running. I'm not saying anything against the other 2 recommendations. Just answering your question πŸ˜‰
  12. What @gebeer said. It could even be as simple as that in /site/ready.php if($page->template == "admin") { if(!$user->hasRole('your-role')) $session->redirect($pages->get(1)->url); }
  13. Great you found the reason. Maybe you can just do a die() or $this->halt() after $pdf->show() ?
  14. Yeah, that's something I'm not sure about yet. I thought of maybe adding a minimum PW version and a maxium PW version that makes sure that the fix is only loaded on versions between that numbers. AOS is great, but it has lots of enhancements and it does not make it easy for anybody to contribute. PwQuickFixes should really only contain fixes of "real" issues that are reported in the pw issues repo (see the updated readme). And it should be really easy to add your own fix file, add the link to the issue report and optionally add pw minimum and maximum versions and tick a checkbox...
  15. Hi guys, thx alot for the discussion πŸ™‚ Good point. I think that should not be a problem. If there is an issue with the core, it should be easier to check a simple fix than to fix the issue yourself. If it was a complicated fix, this module might not be the right place for it. I've added @adrian as collaborator on the Repo - the goal is that this project is a "real" little community project πŸ™‚ --- Thx adrian, I've updated the description of the module: --- Actually I think it IS a module for the average user. See https://github.com/processwire/processwire-issues/issues/812 for example. This is a CSS issue that any webdeveloper can easily fix by some CSS rules. The only problem is: How to get the code properly into processwire. There are several possibilities: Overwrite the core css file (easy, but no option, of course) Create a PR (you don't know when it get's merged and you need a workaround until then) Use a module like Admin Custom Files (this works for CSS and JS, but this will not work if you need hooks for your fix) Add your fix via hooks in ready.php (you end up with a mess of hooks in ready.php and you need to copy over code snippets from project to project) Create a module for it (that might be too much effort for most users for simple fixes) The module makes it really easy to apply any kind of quickfix. And it makes it really easy to merge those fixes via PR's (for the ones maintaining this module). --- True! Nothing to add πŸ™‚ --- It's not intended for hacks, it's intended to fix issues that one would report in the PW issues repository until the issue get's fixed there properly. Hope that makes sense πŸ™‚ Thx, that's a good idea, thx πŸ™‚ --- Nice idea. I'm not sure how helpful automatic statistics would be though. I've got bad feedback on my modules implementing google analytics download tracking and numbers where small overall anyhow, so I'm really not sure how much help a "this fix was used 5 times since 08/2019" would be πŸ˜‰ What do you think of a obligatory property for every fix that links to the related PW issue report. This would make sure that the issue is reported in the issues repo, seen by Ryan and users can vote for the issue there (give a thumbs up). That would also have the benefit that users can raise their voice there, comment things, add screenshots etc.; A lot better than some strange number where nobody knows what it shows exactly... --- Could you please try to do that on your own? I've added you as collaborator πŸ™‚ --- Thx again for all your contributions! Have a great week.
  16. Hi @alexmercenary, I can't reproduce what you are describing:
  17. Not all, but all that are necessary (or at least useful) for other projects and users as well. Not sure what others think of that idea, especially @adrian @Robin S ?
  18. Yeah, the idea is to have a shared place where we can apply those fixes and do not have to wait for core fixes. The benefit compared to placing hooks into /site/ready.php is that we can share our code, it's easier to test in different environments and we can provide better suggestions for a fix to ryan. PS: Happy 1000 @wbmnfktr πŸ₯³
  19. Sorry for the confusion πŸ™‚ There are several issues with the PW core. Some of them get fixed quickly, some don't. All those issues exist on every project and one has to fix them on every project. This module makes it easy to place fixes in a central place and activate them one by one. It was just a quick idea when I read this comment today: https://github.com/processwire/processwire-issues/issues/802 I've just added a fix for the annoying 404 error: https://github.com/BernhardBaumrock/PwCoreFixes/commit/c4fa410654d0d4a4f8a50c53315a350cdf60d347
  20. PwQuickFixes This module is intended to serve as a collection of ProcessWire fixes that can easily be enabled via checkboxes in the module's config. It is NOT intended to be a replacement for github issue reports or pull requests! The idea is that we have a place where we can put fixes for issues that are not yet fixed in the core until they get properly fixed there. It is also not my intention to put pressure on Ryan to fix issues quicker. The idea is that we have a place where we can share our fixes across projects and across users and maybe get a better feeling on the "impact" of different issues. The module could also make it easier for Ryan to test issue reports and the solutions provided by the community: Intended Workflow Identify an issue Create the related files in the fixes folder of this module Create a PR so that I can merge the fix and everybody can use/test/improve it Create an issue in the official PW issues repo and link the fix in your description Usage Just add your fixes in the fixes folder and activate them in the config of this module (via checkbox). See the Foo example module how to add JS and CSS. https://github.com/BernhardBaumrock/PwQuickFixes
  21. Thx, then I think it's probably the best time for creating seperate accounts for them πŸ™‚ What if one user has the same page opened in two tabs? This would be the same session but could also be unwanted (and overwriting/losing changes).
  22. What does the devtools network tab say?
  23. Hi Ryan, thank you! That's a very welcome addition! 😎 I'll buy it soon. One quick question: How does it handle situations when some people share the same PW user to log in and edit pages?
  24. Setting the icon markup of the wrapper does not work, because this also affects all following inputfields and always sets the same icon on all inputfields. This is what I came up with now: // add method to set icon of inputfield manually $this->addHook("Inputfield::setIcon", function($event) { $field = $event->object; $name = $field->name; $icon = $event->arguments(0); $field->parent->addHookAfter('render', function($event) use($name, $icon) { $search = " for='Inputfield_$name'>"; $event->return = str_replace( $search, $search."<i class='$icon'></i> ", $event->return ); }); }); Usage is even simpler: $field->setIcon('fad fa-link');
Γ—
Γ—
  • Create New...