#TYPO3 Bubble: Hat hier jemand eine v11 oder (besser: und) v12 Multisite Installation mit mehreren unterschiedlichen Domains? Ich habe ein potentiell (mittleres) sicherheitsrelevantes Problem entdeckt und es würde helfen zu wissen, ob das bei anderen Setups auch reproduzierbar ist (einfacher URL-Aufruf, Impact erkläre ich dann).
Does getting started with #drupal module development seem intimidating to you? Let me try to provide a dose of confidence - join me on June 8 at DrupalCon Pittsburgh for a full day of the basics:
#WCUS bringing in professional speakers who are not involved in the #WordPress community is interesting, but are we suddenly going to pay speakers?
What is going to motivate people who don't care about the community or who have never heard about it to travel and speak for free? 🤔 I'm seriously questioning how realistic this is.
@davidbisset Companies do pay for expenses - at many large conferences, most if not all, the speaker slots are actually bought by companies because they are included in sponsorship packages. So the event gets paid to have the speaker versus having to pay the speaker. I've sponsored events just to get a guaranteed speaking slot and I would 100% do it for WCUS. But I would expect to be able to have my logo on slides, etc.
This could be a route to go, it just changes the feel of the event.
Plodding through my #wordpress install for my personal site was going pretty good until I tested my contact form and found that WP was not sending those emails. Not sure what is going on, but it's time to take a break.
@clankgy1 Setting up outgoing mail is as easy as giving a smtp server, username and password in most cases. Not much to 'bork'. If the API does something dumb, just use the Gmail server stuff instead.
@arnandegans I did end up using the gmail stuff. Turns out the theme I was using (or maybe it is pr4esent on all themes) has a contact tab in the Theme Appearance tab. Properly configuring that solved the NDR issue.
After a bit of digging, I discovered that they effectively implement at least one interface (StreamInterface) and since they also still support PHP 5.5+, they have not types, and hence PSR-7 actively broke their implementation: https://github.com/aws/aws-sdk-php/issues/2681
@alessandrolai@phpfig I’m not worried about the couple broken installs, more the “this is a breaking change and we have to support 5.5” in the responses. Might signal it can be a while before they unlock the new version for those dependent on AWS (lots of people)
@frankdejonge@phpfig they pinned against ^1.0, so users are still able to install 1.1, which is the intermediate version; libs that are more forward with the implementation are suggested to pin against ^1.1|^2.0, since pinning against 2 only doesn't make sense, so... I don't see the issue? Apart from suggesting them to bump it in four months from now 😁
That is exactly how I envisioned the evolution and adoption of such releases when I wrote the bylaw.
I was quite active in #WordPress development from 2004 till ~2021. I've created multiple large custom WP installations, built plugins, contributed to Core, spoke at WordCamps etc. People considered me to be a WordPress expert. I have a Masters degree in #InteractionDesign.
Today I've tried Full Site Editing using the default theme. After an hour trying to coax Gutenberg into the simple design I wanted I had to give up.
Is it just me or is FSE a horrible #UI#UX experience & buggy as hell?
@arnandegans It is truly bizarre if WordPress experts cannot work with a new featured due to it's unworkable / unusable / unclear. I wonder what WordPress laymen make of it?
@BjornW yep, it’s insane really. I stopped using Wordpress because of it and now use @classicpress . No Gutenberg nonsense for me thanks.
I’ve tried Gutenberg a few times though, see if it finally works or improves my workflow, but no luck so far, it only hinders what I do.
Apparently, partsmof the #PHP Reddit community is considering "#Laravel to be harmful".
This post is making a great point: calling X "harmful" doesn't start a good discussion.
Also, the discussion that is being had seems weird. The Facts: you can make a living with it, maintain projects for years and years, and have useful conventions. The Opinions: it's not working well. (Although it is working, which is worth a lot!)
@ctietze The PHP subreddit has been a pretty toxic mess for years. Better lately, but they sure do love to hate on Laravel and Wordpress. Despite Wordpress being the reason that PHP is still relatively popular, and Laravel being the easiest way to get developers into the language imho.