View allAll Photos Tagged frontend
Denise Jacobs - Infinite Possibilities (Closing Keynote)
Photo by Florian Ziegler, florianziegler.com
The fourth Pixel Pioneers Bristol conference at the M Shed on 10 June 2022. Photography by Adam Gasson.
Off course, the registration is also possible in digital form, directly from your mobile phone.
Photo by Florian Ziegler, florianziegler.com
This photo was captured at the 2018 edition of Great Indian Developer Summit (#gids18), April 24-28, Bangalore, India.
Eva-Lotta Lamm (@evalottchen) during her talk, which she sketch-noted simultaneously while speaking.
Photo by Florian Ziegler, florianziegler.com
Eva-Lotta Lamm (@evalottchen) during her talk, which she sketch-noted simultaneously while speaking.
Photo by Florian Ziegler, florianziegler.com
This craptacular error really shouldn't be happening to the frontend of the main Joomla! site. All indications suggest that this sort of error is primarily a backend issue as seen here:
forum.joomla.org/index.php?topic=32307.msg183857
Since when have the backend errors started promiscuously advertising themselves as part of the frontend ? (I wasn't even logged into the dev network either)
Usually when I've seen this sort of thing elsewhere (outside of a CMS I know and love), it just screams security hole/XSS/"hack me now"..
I've raised this with the OpenWP crew, just to make sure that it's not the integration port that's faulty. OSS projects usually don't ban people for posting a bug report, do they?