netcarver

I know @ryan was on holiday in Europe last week.

Hope you have a great birthday!

Hello all, I have a requirement coming up soon and am looking for advice or suggestions for a library that might allow me to quickly and easily extend PW uploads such that uploaded images can optionally have text, arrows, and simple bounding box overlays, added to them when they are uploaded into a PW image field. This is something I've not done before as I've always used flameshot when annotating images locally prior to upload. I'm looking for something that would preferably allow an overlay layer to be used that could be edited later if needed (for changes/corrections that don't need to change the image.) However, just getting an overlay onto an image in the first place would do for the prototype stage. Thank you in advance for your advice.

@froot Hi there - thanks for asking but I've not looked at this for a number of years, and I doubt I'll get to it any time soon.

@Sanyaissues Please could you try again. I've updated the module to work around what looks like a limitation in the way the module directory parses the requirements defined in module files.

@Sanyaissues Thank you - I can reproduce this now and will dive into it this evening.

@Sanyaissues Thanks for reporting. I must admit, I'm stumped by this as the PHP looks OK to me - it's a simple string concatenation. Perhaps @ryan can chip in and let us know if the module loading code tries to find the PHP string by pattern matching on the text of the module file, rather than running the function - though I doubt that's the case. Anyway, could you try replacing the getModuleInfo() function with the following in the WiremailPostmark.module.php file... public static function getModuleInfo() { $php_version = 'PHP>=' . self::MIN_PHP; return [ 'name' => self::MYCLASS, 'title' => 'WireMail for Postmark', 'author' => 'Netcarver & Pete of Nifty Solutions', 'summary' => 'Allows Processwire to send transactional email via Postmark', 'href' => 'https://postmarkapp.com', 'version' => '0.5.3', 'autoload' => true, 'singular' => false, 'permanent' => false, 'requires' => [ 'ProcessWire>3.0.33', $php_version, ], ]; } ...and try reloading and installing the module? Please post a screenshot of the errors (if any). Also, what version of ProcessWire are you running? Thanks.

@poljpocket It's certainly faster now - the load time for me is now down from multiple minutes to ~13 seconds. The main issue now seems to be the 50MB header.mp4 video.

@poljpocket Thanks for posting that. Looks good, but I'm experiencing extremely slow page loads on the "Meet the team" page. Some of the staff images have been loading for well over a minute. (Chrome or Firefox, both the same.)

Thanks @FireWire, @Andi Actually, that dependency problem broke both timeshift and pacman - so I had to resort to... # SKIP_AUTOSNAP=1 pacman-static -Syu to skip timeshift snapshots (I'm using BTRFS) and use the staticly linked version of pacman. Also removed the offending AUR install of cutycapt-qt5-git and qt5-webkit, and now all is good.

Manjaro here as well - though I have had a few issues with updates due to an AUR dependency on an obscure qt5 package that left things broken and pacman non-runnable. Had to use a staticly linked version of pacman to fix things.

Carousel of some kind, rotating through all the logos? Not sure I like it, but it might work.

Yes, I switched from Windows to desktop linux in 2004 and have not regretted it. I do have a Windows VM for running one legacy app, which I boot once every 2 months and run for a few hours. Apart from that I also use DDEV to run local development containers (thanks for the pointer @bernhard) and am using the Cinnamon desktop - which I do prefer over gnome.

Don't you need to sanitize encode (selectorValue) your variables before you use them in your get selector?

Hmm. What's your .htaccess like? Could this be related? Also referenced is the page name whitelist. I wonder if these are kicking in somehow for the slug. # PW-PAGENAME # ----------------------------------------------------------------------------------------------- # 16A. Ensure that the URL follows the name-format specification required by PW # See also directive 16b below, you should choose and use either 16a or 16b. # ----------------------------------------------------------------------------------------------- RewriteCond %{REQUEST_URI} "^/~?[-_.a-zA-Z0-9/]*$" # ----------------------------------------------------------------------------------------------- # 16B. Alternative name-format specification for UTF8 page name support. (O) # If used, comment out section 16a above and uncomment the directive below. If you have updated # your $config->pageNameWhitelist make the characters below consistent with that. # ----------------------------------------------------------------------------------------------- # RewriteCond %{REQUEST_URI} "^/~?[-_./a-zA-Z0-9æåäßöüđжхцчшщюяàáâèéëêěìíïîõòóôøùúûůñçčćďĺľńňŕřšťýžабвгдеёзийклмнопрстуфыэęąśłżź]*$" # END-PW-PAGENAME