AdultZone

Archives

3 Ways to Add a WordPress Chatbot to Your Website for Free (With Step-by-Step Tutorial)

The fastest and easiest way to add a chatbot to your WordPress site is with Hyve, a free WordPress chatbot plugin. It offers enough bandwidth for most light-traffic sites, such as personal blogs, smaller ecommerce stores, or sites representing a local brick-and-mortar business. If you have more extensive needs, it also offers a reasonably priced… The post 3 Ways to Add a WordPress Chatbot to Your Website for Free (With Step-by-Step Tutorial) appeared first on Themeisle Blog.

Matt: Me.sh on Android

TechCrunch on how Me.sh (née Clay) is now available on Android. Also, kudos to those other Clay folks for winning the Clay memetic namespace dominance.

WordPress.org blog: Introducing the WordPress Browser Extension

The official WordPress Browser Extension is now available for Google Chrome and Chromium-based browsers in the Chrome Web Store and for Safari on macOS in the Mac App Store. This new open source extension lets logged-in site users easily hide the admin bar while keeping its most helpful shortcuts in the browser toolbar, provides quick access to all of your WordPress sites, and adds helpful tools for developers and content creators. By default, the admin bar sits at the top of every page you view while signed in to WordPress, keeping the dashboard, the editor, and your profile within reach. That convenience carries a cost: the bar occupies the viewport, so the page on screen is never quite the page a visitor sees. On sites doing more interesting things with the viewport, such as sticky headers or scroll-driven effects, it can introduce artifacts that send you hunting for a bug that is not there. Further, the admin bar can sometimes grow unwieldy as plugins add their own features and shortcuts to it. Switching it off in your profile settings trades one problem for another, because the shortcuts leave with it. That problem was the spark for the creation of the WordPress Browser Extension. The extension hides the admin bar on the sites you choose, or everywhere by default, and keeps the most commonly used shortcuts one click away. Bringing the full bar back takes two clicks and no trip to the dashboard. What began as a fix for that one tradeoff grew into something broader: a way to recognize WordPress wherever you find it on the web, to jump into your own sites from anywhere, and to carry a small set of tools for testing and review. As you browse, the toolbar icon shows whether the current site runs WordPress and whether you are signed in, without being obtrusive. On a site you manage, opening the extension reveals shortcuts to the dashboard or to the editor for the exact post, page, taxonomy, or template in view, including template-backed pages that open in the Site Editor on block themes. A locally stored launcher remembers the sites you sign in to, so they stay available even when you are somewhere else entirely. A few tools also turn out to be a better fit for the browser than for a WordPress plugin. The extension can draw block boundaries over the rendered page, open a phone-sized preview window, reload with cache busting, or clear cookies and local storage for the site you are on. Some of that is hard to do from inside a site, and none of it requires a plugin or any other software installation, so the same tools are available on every WordPress site you visit. All of this happens on your device. The extension reads the page in front of it to work out what it is looking at, and when it needs more than the page can tell it, it asks the site. Your preferences, and the list of sites you sign in to, stay in your browser. Nothing is sent anywhere else, and there is no tracking or analytics of any kind. The extension began as an independent project and became an official project with active support from Matt Mullenweg. Notable contributors include Fabian Kägy, a core contributor and colleague at Fueled (formerly 10up), who helped shape much of its early design and architecture, and Khokan Sardar who contributed multiple patches. Several other Fueled colleagues provided comprehensive testing and influenced its final shape. You can follow along with its development on its GitHub repository, where bug reports and pull requests are welcome.

WordPress.org blog: WordPress 7.0.4 Release

WordPress 7.0.4 is now available WordPress 7.0.4 is now available which features a security fix. Because this is a security release, it is recommended that you update your sites immediately. You can update to WordPress 7.0.4 by downloading it from WordPress.org, or visiting your site’s Dashboard → Updates and clicking Update Now. Sites that support automatic background updates will begin updating shortly. For more information, please visit the WordPress 7.0.4 HelpHub site. Security update included in this release The security team would like to thank the team at pwn.ai for responsibly reporting the following vulnerability and allowing it to be fixed in this release: Authenticated Author+ remote code execution via malicious file upload on sites that use Imagick and Ghostscript. Backports As a courtesy, these fixes are being backported through to the 4.7 branch and the 7.1 RC3 release that’s due later today. As a reminder, only the most recent version of WordPress is actively supported. The backports are in progress and will ship as they become ready. CVE and GHSA references Further details can be found in the advisory: CVE-2026-65640 / GHSA-8vr3-7mxf-gx8w. Thank you to these WordPress contributors This release was led by John Blackbourn, with significant input from Dennis Snell and Jeremy Felt. In addition, WordPress 7.0.4 and its backports would not have been possible without the valuable contributions of the following people: Aaron D. Campbell, Aaron Jorbin, Adam Silverstein, Aki Hamano, Alex Concha, Barry, Dennis Snell, Ehtisham Siddiqui, Jeremy Felt, John Blackbourn, Jonathan Desrosiers, Lance Willett, Marin Atanasov, Mohammad Jangda, Sergey Biryukov, vortfu, Weston Ruter, and representatives from WP Engine.

#229 – Amy Kamala on Art, Tech, and Open Source: A Journey Through WordPress and Community

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, what draws people into the work of open source projects. 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 Amy Kamala. Amy’s journey into tech is anything but conventional, starting with a master of fine arts from UCLA, and a passion for art that eventually bled into, and was overtaken by technology. Since 2018, she’s been an active contributor to WordPress, serving multiple teams such as the Hosting and Core Teams. Her career zigzags through key roles at DreamHost, InMotion Hosting, Pantheon, Canopy Studios, and local government. Picking up everything from technical support and web development, to managing teams of designers and DevOps staff. Along the way, Amy has organised WordCamps, led teams, and is currently being sponsored by Elementor for her open source work. Today’s conversation gets into the chaotic, creative, overlap between art and tech and how those different mindsets can feed one another, especially in the world of WordPress. We talk about the blend of creative and logical thinking needed in web development and why skills like user experience, curiosity, and even willingness to fail publicly can set you apart. We then turn to contribution. What draws people to volunteer in an open source community? What Amy gets out of participating far beyond her paid hours, and the messy journey from being an eager helper to an essential part of the team. She explains the unique feeling of the WordPress community, the importance of being welcoming to new contributors, and why being outgoing and not afraid to ask questions can be your biggest asset. If you’ve ever wondered about the blurred lines between arts and code, why people throw themselves into volunteer work in the WordPress ecosystem, or what’s really at the heart of this global community, 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 Amy Kamala. I am joined on the podcast by Amy Kamala. Hello, Amy. [00:03:22] Amy: Hello. Thank you for having me. [00:03:24] Nathan Wrigley: You’re very welcome. Amy was introduced to me by Jonathan Desrosiers, who’s been on this podcast many, many times before. I don’t exactly recall the nature of that introduction, but I’m very glad to have you on the podcast today. The intention really is to have a broad, wide-ranging, no-holds-barred conversation, I think about contribution, why people do it, and the community in general. So we’ll see where it takes us. Amy, firstly, thank you for joining us, and I wonder if you wouldn’t mind just telling the listeners a little bit about yourself. Honestly, you can go in any direction you like with that. Maybe if you, I don’t know, bind it to WordPress or contribution or whatever it may be, that would be good. [00:03:59] Amy: Thank you too. Thank you so much for having me. I’m happy to be here. So I’m from Venice Beach, California, and I’m actually an artist and my background is in art. I have a Master of Fine Arts degree from UCLA. But a lot of my artwork was supported by technology, and at some point, technology crossed over, took over, and now my technology is supported by artwork. I’ve been contributing to WordPress since 2018. In 2019, I became a team rep for the hosting team, and I am now on my sixth non-consecutive year as a team rep. And this year I’m also a Core team rep, which has been really fun and I love working with both teams. I started working in the tech industry in 2015 in social support for web host, DreamHost. I was there for about five years, a little bit less than five years. I worked my way up from social support to technical support to live chat, and then helped form a specialised WordPress support team. And I was taking escalations, training team members, devising and documenting team processes. And while I was there, I helped strategise and implement new WordPress products which made revenue in beta, and that was really fun. I got to work directly with the CEO and the VP of product, and I learned a lot doing that. Then I left, and I became a tech lead at a web dev agency, and then the pandemic hit, and we all know how that went. And then in 2020, I started working for InMotion Hosting as their web development manager. I was responsible for over 23 online corporate assets, five web servers, multiple Jira projects, and also the supporting infrastructure, the DevOps pipeline, GitLab, so on and so forth. And I loved that. It’s actually, that was one of the best jobs I’ve ever had. They’re a great company. It was amazing working there. I had an amazing boss. Totally great. I still have friends from there, and from DreamHost for that matter. And DreamHost was also great. I have a special love in my heart for DreamHost. I’ve known those guys for a really long time. And then I was recruited by Pantheon to be a solutions architect for their professional support team. That didn’t work out for me as I had hoped, and