Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/05/2021 in all areas

  1. The next dev version of ProcessWire is in progress but I'll wait till likely next week to bump the version. So far there are 6 new pull requests added since 3.0.179 and 2 issue resolutions, plus some other updates, with plenty more on the way. A lot of focus this week has also been on FormBuilder updates which include new spam filtering options, improved save-to-page options, improved Combo field support, new entries actions (and the ability to add more via modules and hooks), framework updates, and various minor bug fixes. This version has a lot of nice improvements and I'm hoping to have it ready for you in the next week or so. More details soon. Have a great weekend!
    11 points
  2. I made a small update where you can now output the QR Code on the front-end by calling the field directly (instead of rendering the inputfield) and I added the option to output the image in either .svg or .gif (if .svg, you'll have the additional ability to output the markup directly, instead of a base64).
    4 points
  3. The usual way that I would do it is to create a service URL* on the 2nd website, which returns JSON to the ajax request, if you're going to load the comment markup and form via ajax. Alternately you could use an iframe, so the 2nd website would have an output template to render the comments thread and form; this could be a single template/page with get params; I don't see any benefit or reason to use multi-site / multi-instance (but maybe i'm missing something), unless it makes managing comments for an article easier; but you could also create a field in the comments site that pulls in the title or other info from the main install, using a service page on the main install, returning JSON response; In terms of the service "page" or URL - there are some new api features that will allow you to have a service URL without having to actually create a page as an endpoint. https://processwire.com/blog/posts/pw-3.0.173/
    2 points
  4. This may be because only copies can be stolen, never the originals ? But all joking aside. If you want to protect the images at some point, you will probably not get around a very present watermark in the images for the large representations. Additionally you have to prevent access to the original images for non-registered visitors. Both would not be of much work. Example: Watermark a variation of the original images directly (in the same size) and then always use this WM-variation as the starting image for all further image processing. This could be encapsulated in a function or better maybe directly hooked as a new Pageimage->Function or Property. You would then always call your images like $image->wm->width(1280) instead of $image->width(1280). The possibility to create variations without watermark still remains. If you are interested I could create a tutorial for everyone. For watermarking we have the old but still working module PIM2 and for protection there is a description how to set this up. If you are interested I can fast-guide you through this via PM or E-Mail. ?
    2 points
  5. Hi Chris, I have yet to see any issue with image theft. Partly that's probably because the site doesn't get a whole lot of traffic. ProcessWire is far better at handling images than anything else I've used, and I don't utilise it's full potential.
    2 points
  6. Here is my website, built with ProcessWire, and still being refined as I learn more. https://robpackerphotography.com/ My website journey has taken me via plain html, Singapore (anyone remember that?), Wordpress, modx, and now finally PW. Along the way I experimented with drupal, concrete, silverstripe and a few others that I'd rather forget. All self-taught and done between full-time work, family and a passion for photography. I have found using ProcessWire relatively simple - despite the steep learning curve of having to learn about php... The community support is fantastic.
    1 point
  7. For this to work, one needs to modify PW's root .htaccess at "# 4. Protect from XSS with Apache headers" of the "loaded site", something like: <IfModule mod_headers.c> # prevent site from being loaded in an iframe on another site # you will need to remove this one if you want to allow external iframes # Header always append X-Frame-Options SAMEORIGIN # Lets the listed domains load content into an iFrame Header always append Content-Security-Policy "frame-ancestors 'self' example.com example.test www.anotherexample.com;" also, it is probably a good idea to turn the iframe into a responsive container: https://github.com/davidjbradshaw/iframe-resizer
    1 point
  8. Note that rename() will not rename variations... you should track changes on basename: $p->singleImage->trackChange("basename"); $image->removeVariations(); $image->rename($newFilename); $p->save("singleImage"); https://processwire.com/talk/topic/4299-how-to-rename-a-file-properly/?do=findComment&comment=42213
    1 point
  9. May Lister be good for rapido online restaurant e-menu development ? We need option for user to see menu items with photo , description , price and to select many item they wish to order. Maryla can take order over phone and customer love services but some time we better should like user to check out online so it sends message direct to kitchen while Jeffry prepare queso frijoles, especial daily, chorizo fermentado, el stanko salchichón, meat boat, and other customer favorite. Most customer take out since covidiarrhea real concern here so we wish to improve our e-portal online menu. Greetings from home of Roderigo Kitchen, best wishes and thanking you.
    1 point
  10. I can provide a module for this usecase: https://github.com/kixe/AdminHidePageTreeByRole ... or try one of them: https://processwire.com/modules/admin-restrict-page-tree/ https://processwire.com/modules/admin-restrict-branch/
    1 point
  11. Don't mess with @teppo. He sees and knows almost everything and therefore we love him so much (but don't tell him). Thank you as well for your module. This might and will be a great addition for a lot of us.
    1 point
  12. Cool! Looks like we gotta gave a theme switcher module.
    1 point
  13. Just a quick test: dark theme. For anyone interested, here's the admin.less file: admin.less
    1 point
  14. @dadish I've created a PR to support $page->references: https://github.com/dadish/ProcessGraphQL/pull/33 It works in my side and was very quick to implement. Kudos for such good structured module ? EDIT: Just saw there is an other PR with implementation of this. Maybe you can check both...
    1 point
  15. I made a fork because i needed some changes for my use - maybe it can be useful. https://github.com/dauni/TextformatterSrcset/releases/tag/1.0.6
    1 point
×
×
  • Create New...