AdultZone

Archives

WPBeginner Spotlight 28: WPVibe Hits 40,000 Sites, a New WPForms Dashboard, and Two WordPress Security Updates

September was the month WordPress plugins really started talking to AI assistants in a serious way. You can now manage backups, forms, online stores, and fundraising campaigns just by asking Claude or ChatGPT, and there’s a good chance you already have some of these plugins… Read More » The post WPBeginner Spotlight 28: WPVibe Hits 40,000 Sites, a New WPForms Dashboard, and Two WordPress Security Updates first appeared on WPBeginner.

WPTavern: #235 – Rob Pugh and Tony Arcangelini on Bringing Podcasting to Jetpack

Transcript [00:00:19] Nathan Wrigley: Welcome to the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcast which is dedicated to all things WordPress, the people, the events, the plugins, the blocks, the themes, and in this case, bringing podcasting to Jetpack. If you’d like to subscribe to the podcast, you can do that by searching for WP Tavern in your podcast player of choice, or by going to wptavern.com/feed/podcast, and you can copy that URL into most podcast players. If you have a topic that you’d like us to feature on the podcast, I’m keen to hear from you and hopefully get you, or your idea, featured on the show. Head to wptavern.com/contact/jukebox, and use the form there. So on the podcast today we have Rob Pugh and Tony Arcangelini. Rob and Tony are longstanding members of the Automattic team with extensive backgrounds in marketing, product, and software development. They’ve spent years building tools for creators, writers, podcasters, and everyone in between, and now they’re fully immersed in WordPress’s evolving podcasting capabilities. If you’ve been looking for ways to run your podcast from your own WordPress site, this conversation is for you. Rob and Tony dive into the new Jetpack podcasting features, and why they made the leap from WordPress.com’s basic audio offerings, to a more robust, integrated solution, within Jetpack. They talk about what makes WordPress and Jetpack such a powerful home for creators. The ability to bring your newsletter, blog, podcast, and all your content and communication under one roof, all while keeping ownership of your data. We talk through the advantages of keeping your content out of walled gardens like Substack and Patreon, and the value of flexibility, whether that’s adding WooCommerce to sell merch or customising your site’s look. Rob and Tony breakdown just how easy it is to start your show. Drop audio into a post, set your category, and let Jetpack handle the rest. From distributing your RSS feed to major podcast apps, to sending out newsletters, and automated social posts. They also get into how integrations with PocketCasts and Jetpack AI make content creation, transcription, and distribution smoother than ever before. Plus how WordPress is open Foundation promises you’ll never be locked in. If you are a creator wondering how the next generation of podcasting fits into the WordPress ecosystem, or just want an easier way to launch and grow your show, this episode is for you. If you’re interested in finding out more, you can find all of the links in the show notes by heading to wptavern.com/podcast, where you’ll find all the other episodes as well. And so without further delay, I bring you Rob Pugh and Tony Arcangelini. I am joined on the podcast by Rob Pugh and Tony Arcangelini. Hello, both. [00:03:23] Rob Pugh: Hey, how’s it going, Nathan? [00:03:24] Tony: Hello, Nathan. [00:03:25] Nathan Wrigley: Nice to have you both with us. Today we’re going to be talking about something which is actually genuinely dear to my heart because we’re going on about podcasts. Yay! I’ve been in the podcasting space for decades, and WordPress has been the place where I’ve done it every single episode. I’m entirely indebted to WordPress for the capacity to do all of the podcasting I’ve done. But I’ve never done it inside of Jetpack, because until recently, I don’t think that was possible. So that’s what we’re going to talk about today. First of all, I’ll just go round the houses. I’ll start with Rob. Would you mind giving us just a quick potted bio of what it is that you do over at Automattic, Jetpack, whatever it is that you want to mention. [00:04:04] Rob Pugh: Yeah, so I’ve worked at Automattic for seven years. I’ve been in marketing and now focused more on product, but I like to do a bit of everything. And I work mostly with tools for people that create stuff. So podcasts fit right in there, and we are excited to build out this feature. [00:04:19] Nathan Wrigley: Nice. Thank you. Tony. [00:04:21] Tony: Yeah. I’ve also worked for Automattic for about eight years now. I do software development, and so I have had firsthand in building everything that we’re talking about today. [00:04:31] Nathan Wrigley: Okay, thank you very much. Now, just before we started recording, I was on the call with Tony before Rob joined in and you labored the point, not labored, but you mentioned that you were in the sort of creator side of Automattic. I didn’t know that existed, but that to me is about the most interesting bit of any organization. You know, the bit where the musicians come, and the poets come and the writers come and the podcasters, and the videos and the YouTubers, and all of that come. I think that’s really interesting, and I didn’t realise there was a wing of the business entirely aligned to that. But I guess I’ve been schooled, and now I know. So podcasting definitely comes under that banner. Okay so I didn’t know this existed, and I think it didn’t exist, but maybe Tony can redirect me a little bit here. Podcasting in the WordPress space, I think you could do more or less everything that we’re about to talk about inside of wordpress.com until recently, but now it’s shipped inside of Jetpack. First of all, I’ll just send that one to Tony. Is that true? Is this all like a port of things into Jetpack from .com? [00:05:32] Tony: I’d say it’s a little bit more than a port. So we built a very basic feature of podcasting in WordPress.com to offer WordPress.com users. It was very basic. It was just the feed. Basically what you see in the free offerings right now. The ability to drag an audio into a post and for that post to then become a podcast episode. And then we had a curated RSS feed that was available.

bbPress: bbPress 2.6.19 is out!

bbPress 2.6.19 is a security and maintenance release. Everyone running bbPress should update. This release applies inherited forum passwords to REST API responses and BuddyPress activity, and strengthens access checks for restricted forum content across feeds, group forums, and other indirect views. It also tightens moderation and forum-role permissions, protects importer credentials and account handling, and improves escaping in profile and administration output. There are maintenance fixes for BuddyPress group-forum associations and notifications, converter cleanup, imported database passwords, subscription emails, and reply positioning. The 2.6.19 upgrade notes cover integration details. bbPress still requires WordPress 6.0 or newer and PHP 7.2 or newer. The automatic database version 264 upgrade clears saved converter query SQL from older password upgrades. These changes are also in the 2.7 development branch, which is now 2.7.0-alpha-4. Thank you to thewindghost, ngonhuy, and moltenbit for responsibly reporting issues fixed in this release, and to everyone who helped review and test the changes. Download bbPress 2.6.19 from WordPress.org, or update from your WordPress dashboard.

HeroPress: From Blogging to Belonging: My WordPress Journey – Blogging से Belonging तक: मेरी WordPress Journey

वर्डप्रेस ने मुझे मेरे ज़िंदगी में कुछ अलग करने का मौक़ा दिया। Introduction My name is Satyam Vishwakarma, though most people know me as Satya. I come from a small village called Mahmadpur, near Fatehpur, the city of Doaba, in Uttar Pradesh, nestled between the sacred Ganga and Yamuna rivers. This is the place I’ve always called home. I studied Electronics Engineering (Micro) at Government Polytechnic College in Fatehpur. Growing up and studying in a relatively small city, I never had a clear idea of where technology or the internet could take me. Satyam Vishwakarma presenting his project during the first year of his diploma, 2018. I didn’t discover WordPress with a big career plan. I was simply curious about technology and wanted to help the people around me. Most of my classmates, including me, came from Hindi-medium schools or the UP Board. A lot of the technical material we found online was either difficult to understand or simply wasn’t written in the kind of simple English we were comfortable with. At the same time, I was probably one of the more tech-savvy people around me. I loved trying new software, exploring new features, and figuring out how things worked. Whenever I discovered something interesting, I would share it with my WhatsApp groups and classmates. I didn’t think of that as writing or teaching at the time. I was simply sharing something I had discovered. Eventually, I thought: why not put some of this information somewhere that more people could find it? That small thought became the beginning of my writing career. Before WordPress, there was Blogger Some of my earliest opportunities to write online came through people I met on WhatsApp. I became friends with Mohit Vyas and Arpit Nuwal through one of the technology-focused WhatsApp groups I was part of. They had built a website called TopJankari. It wasn’t running on WordPress. It was a custom-built, dynamic website with its own basic way of managing content, but it was still fairly simple compared with the content management systems I discovered later. I started writing technology and tips-related content for TopJankari. For me, this was exciting. I was taking the things I was already experimenting with and turning them into something that other people could actually read and use. Around the same time, I started experimenting with Blogger.com and began publishing my own technology and tips-related content there. I wasn’t thinking about becoming a professional writer. I just enjoyed technology; I enjoyed explaining things, and I liked the idea that something I wrote could help another person solve a problem. That was enough motivation to keep going. Then WordPress entered the picture While I was experimenting with blogging, my brother Shivam (now runs a WordPress design agency called Subhash Digital) built his first website with WordPress. That caught my attention. I was already curious about how websites worked, and seeing him build something with WordPress gave me an idea of what was possible. I wanted to try it myself. Around the same time, my brother Kapil and I started learning WordPress together. Neither of us really knew what we were doing. We learned through YouTube videos, documentation, blog posts, and mostly through experimentation. We would try something, break it, search for why it broke, fix it, and move on to the next thing. My first WordPress project was EngineersGuru, a place where I could share content related to my Electronics Engineering (Micro) course. I initially ran it as a subdomain, with the idea of making useful course-related tutorials and information easier for fellow students to understand. We also started an Android-related blog and Jankari.xyz, a more general website where I could write about pretty much anything I found interesting. In hindsight, those websites were my playground. They were where I learned WordPress, writing, SEO, content creation, and the basics of running websites. I wasn’t following a carefully designed career path. I was just building things because I wanted to see what I could do. And that curiosity kept taking me somewhere new. Learning by failing As I continued blogging, I started learning about SEO, monetization, and affiliate marketing. I experimented with different kinds of websites and eventually built more than ten blogs while I was still learning. One of my projects eventually became EYNZone (formerly known as EYNWorld), where I started helping others learn WordPress and other skills and grow their own projects. There were plenty of failures along the way. I applied for Google AdSense more than twenty times before I finally stopped guessing and actually studied the guidelines carefully. Eventually, I got a brand-new domain approved with only two articles. That experience stayed with me. It taught me that rejection doesn’t necessarily mean you aren’t capable. Sometimes you simply haven’t figured out the problem yet. That became a recurring theme in my life. Looking for a career, finding a community Eventually, I started looking for a full-time job in mid 2022. That was another learning experience, although not always a pleasant one. I applied to more than 800 companies and went through around 2,000 job applications. During that period, I discovered UnderrepresentedInTech through Michelle Frechette. That eventually introduced me to Post Status, where I started meeting more people from the WordPress ecosystem. Something interesting was happening. While I was struggling to find where I fit professionally, I was slowly finding a place for myself in WordPress. I started learning not just about the software, but about the project behind it and the people who were building it. And then I heard about WordCamp Bhopal. The WordCamp I almost couldn’t attend My first WordCamp was WordCamp Bhopal in 2023. I wanted to go. I had told people I would go. There was just one problem: I didn’t have the money to actually make the trip happen. So I asked for help in the Post Status Slack community. I still think about what happened next. People who had never met me in person decided to help. Alan, Jenni,

OpenStation Blog: WordPress Has Been Missing This for 15 Years

tl;dr: 15 years stuck in the same wp-admin, why don’t you try in playground the new wp-admin experience? WordPress has spent the last fifteen years becoming capable of doing almost everything, yet somehow we have continued interacting with wp-admin in fundamentally the same way: click somewhere, load another screen, go back, open another tab because you do not want to lose the previous one, and after a while end up with ten different WordPress tabs scattered across your browser. I find it quite funny that we all accepted this as completely normal. Today WordPress is used to run stores, publications, membership sites, communities, LMS platforms, agencies and entire businesses. We have plugins that are effectively full applications, incredibly complex editing experiences, analytics, forms, CRM systems, media tools, commerce, automation and thousands of other things living inside the same installation. Yet the interface connecting all of them still assumes that, most of the time, you want to look at one thing at once. And when you don’t, the browser has to solve the problem for us. Browser tabs have essentially become the window manager of WordPress. That is one of the ideas that eventually led us to OpenStation. Why don’t we have windows? It sounds ridiculously obvious when you phrase it like that, but that is exactly why I find the question interesting. On a normal computer I can have my editor open next to a browser, keep a terminal in the background, drag files around, minimize something I want to return to later, or simply arrange my workspace around whatever I am doing at that moment. Nobody thinks about this as a feature anymore because it is just how computers work. Then we open WordPress and suddenly that whole model disappears. If I am editing a post and need something from the Media Library, I navigate away or open another tab. If I am checking an order while editing a product, another tab. If I want to compare two posts, another tab. If I am configuring something and need to check how another part of the site is set up, another tab. There is nothing technically wrong with that, of course, and it has worked for years, but after building and using OpenStation every day I started noticing how much context we constantly throw away simply because wp-admin was designed around pages rather than workspaces. That distinction matters much more today than it probably did fifteen years ago. WordPress quietly became something much bigger I keep describing WordPress as the operating system of the web, and obviously I do not mean that literally. What I mean is that WordPress has gradually accumulated many of the characteristics you would expect from a platform where applications live. Plugins install capabilities into it. Users have identities and permissions. Applications share data. We have APIs, scheduled processes, notifications, media, editors, databases and an enormous ecosystem of software that knows how to work with the same underlying environment. The strange part is that the interface never fully made the same transition. We kept adding more applications to WordPress, but we continued presenting them largely as destinations in a menu. OpenStation started from a very simple thought: what happens if, instead of redesigning every individual wp-admin page again, we change the environment in which those pages live? That immediately opens a much larger set of possibilities. A post editor does not need to replace your media library on screen. A WooCommerce order does not need to replace the product you were editing. A plugin screen does not necessarily need to occupy the entire browser just because you clicked its menu item. They can simply be windows. You can move them, resize them, minimize them, keep several of them open, organise them across different desktops and return to exactly what you were doing without recreating the context again. The funny thing is that none of this feels particularly futuristic. Quite the opposite. We have been using computers this way for decades. We just somehow never brought that interaction model into wp-admin. The interesting part is not actually the windows The windows are what people notice first because they are visual, but I think the more important idea is what happens once WordPress stops assuming that navigation must destroy context. Suddenly the admin becomes a workspace. You can have the Media Library next to the editor instead of travelling between them. You can keep an order visible while checking something else. You can open notes or widgets without abandoning your current task. Applications can coexist on the same desktop and eventually interact with each other in ways that become much harder when everything is isolated in separate browser tabs. This is also where things like drag and drop become much more interesting. If two applications are part of the same environment, moving an image, a product, a post or another WordPress entity between them can become an actual interaction instead of a sequence of copy, navigate, search, paste and navigate back. And once you start thinking about WordPress this way, a lot of things that initially looked like unrelated OpenStation features start making sense together: windows, the dock, multiple desktops, widgets, the command palette and applications are all different pieces of the same idea. The goal is not to decorate wp-admin until it looks like a desktop operating system. The goal is to make working in WordPress feel less like navigating a website and more like working inside an environment. We don’t need to replace wp-admin to do this This is probably the part I like the most about the approach. WordPress already has an enormous ecosystem and rebuilding everything would be both unrealistic and, in my opinion, the wrong problem to solve. There are thousands of admin interfaces that already work, plugins developers have spent years building, and workflows users already understand. OpenStation can sit on top of that rather than asking the ecosystem to start again. The existing WordPress admin can continue being WordPress. Existing

Open Channels FM: Open Source Champions

The Open Source Champions initiative invites individuals and brands to support the network through a unique advocacy opportunity, offering exposure, promotional features, and participation in special episodes.