I was migrating a tumblr sideblog to wordpress for the first time, and while it was still migrating, I changed the old blog's url. Really dumb move, I know, but it's late, and I was too tired to notice. Is there any way I can fix this because now I'm stuck on migration with the old url and it won't let me change it. I'm not seeing an option to stop this anywhere.
I've had an old website running on Wordpress for years, and I'm finally building a new small site from scratch, but things have changed a lot from when I initially learned the system. I'm trying to do what I thought would be the very simple task of adjusting the size and height of an HTML block I dropped in the editor, but despite searching, I haven't been able to find a way to do this. The block seems to have a fixed, very short height, and a width constrained to a block container I can't identify.
Could anyone point me in the right direction for how to manually set the height and width for an HTML block containing an iframe element?
Esta es mi tercera publicación. Mi proyecto va bien, pero esto me ha resultado frustrante (además de haberme adentrado en el desarrollo de WordPress sin tener mucha experiencia).
Mi cliente no tenía imágenes ni texto, así que primero busqué una plantilla. Pero luego me di cuenta de que sería mejor crear el diseño yo mismo por lo "sencillo" que era, y porque buscar plantillas y luego adaptarlas supone un trabajo extra.
El problema es que tuve que empezar a diseñar sin los recursos del cliente, mientras que él esperaba una plantilla para saber qué debía enviarme. Al final, le pedí a la IA que generara una imagen y empecé a desarrollar algo muy parecido. Pero aunque ya he añadido el texto y las imágenes del cliente, de repente siento que, con mi próximo proyecto, no empezaré hasta que el cliente me haya dado todo.
¿Cómo sueles empezar?
Me encantaría saber tu opinión.
EDIT: I should mention that they gave me a couple of website examples, which made finding a template that matched them quite difficult. And filling in a site like the ones they showed me would still have required their content and resources.
I’ve started to notice that some of the biggest WordPress headaches usually come from small things that were ignored earlier.
For me, keeping plugins/themes updated, removing things that aren’t actually being used, and having regular backups has prevented a few problems from becoming much bigger ones.
I’m curious what it’s been for other WordPress users and developers.
What’s one WordPress habit or practice that has saved you from a major issue later on?
Hi everyone,
I’m currently setting up a site and I'm looking for recommendations, plugins, or tutorials to get a landing page builder experience similar to MailerLite inside WordPress.
I've tried a few traditional page builders and tools, but most of them either feel too bloated, overly complex for simple sales/opt-in pages, or lock essential landing features behind expensive paywalls.
What I need is a builder is that it's clean, intuitive, fast, and completely focused on high-converting landing pages rather than heavy corporate websites.
Does anyone know of a plugin combination, a specific block-based workflow, or tutorials that can help replicate this minimalist, streamlined landing page experience in WordPress?
Any suggestions or setups you use for this would be greatly appreciated!
Hi Reddit Community, I'm in the blogging field from 2007 and you may be laughing that I joined reddit today, the main purpose to join reddit is that I want to explore new ways of blogging, I have done many type of blogging, like event blogging, pSEO Blogging, I have purchased many books and methods and create my own methods, mostly my income is through google adsense, from last 4 months I'm focusing on creating content through AI and using my google sheet+apps script+wordpress rest api for content scheduling, I think recent time is game changing time for bloggers, if they spend some budget on AI Agents for research and content scraping, they can change their life in online field, how many of you agree and please also share if you are working on google sheet + apps script
EDIT: Thank you to u/bluesix_v2 and a few others for teaching me about Must Use Plugins - I had no idea that you could just hide secret plugins in the backend of WordPress that wouldn't show up in the dashboard - after deleting some Hostinger mu-plugins, not only is the problem fixed but my website has suddenly started running ten times faster. THANK YOU!
Exactly as the title says, I can't update WordPress right now because, even after going through all the correct channels to transfer my website from Hostinger to my new host IONOS (yes I know IONOS isn't great but it's cheap and I'm broke), every time I attempt to update WordPress, I get the following error:
"Download failed.: cURL error 28: Failed to connect to wpdownloads.hostinger.io port 443 after 10006 ms: Timeout was reached"
It's clearly still trying to download things through Hostinger, despite the website having been fully transferred away from Hostinger, domain, database and filesystem.
I've cleared all references to Hostinger from the database, removed all Hostinger-related plugins, there shouldn't be anything left of Hostinger in this website, but obviously I've missed something. Does anyone have any idea where this final remnant of Hostinger's code could be hiding in my website?
This is preventing me from keeping my website up-to-date so it's a very pressing issue for me. I'd appreciate any and all help!
What is everyone using for documentation? I’m talking about like to document custom functions or features you’ve added that you (or someone else later on) would benefit from. I use external documentation in a CRM for my own knowledge base, but if seems like there should be some sort of developer’s guide we can leave in WP for future reference.
I maintain the documentation site for a small tool I build, and about a year ago I put an illustrated guide character on every tutorial page, because the audience is not technical and a wall of text was losing them somewhere around step four. Forty one tutorial pages, a hundred and sixty eight illustrations, roughly four per page. This is what that did to the site and what actually fixed it, because most of what I tried first was the wrong lever.
The starting position was bad in a boring way. For the first thirty pages I uploaded whatever came out of the image generator. PNG, about fifteen hundred pixels wide, roughly 1.35 MB each. WordPress then did what WordPress does. Thumbnail, medium, medium_large, large, the 1536 variant, the 2048 variant, three more sizes the theme registers, plus a scaled copy for anything over the big image threshold with the original kept alongside it. Ten files on disk for every one picture on screen. The uploads folder was about 560 MB and roughly sixteen hundred files for what a reader would describe as a hundred and sixty eight pictures. The media library grid took several seconds to paint and every file was called some variant of guide_final.
Page weight was the visible symptom. A typical tutorial page carries four illustrations, so four times 1.35 MB is 5.4 MB, and the theme, fonts, CSS and markup were another 500 KB on top. Call it 5.9 MB for a page whose actual content is six hundred words and two code blocks. Largest contentful paint on a throttled mobile profile was 4.8 seconds. Time to first byte on the shared host it lives on was around 480 milliseconds cold.
Compressing before upload rather than after was worth more than everything else put together. Every illustration now gets resized to nine hundred pixels wide, converted to WebP and compressed, and only then uploaded. That takes each one from 1.35 MB to about 78 KB. The ordering is the whole trick. If compression happens inside WordPress after upload, the library is still storing a large original and generating all its derived sizes from it, so the disk cost stays. If the file is already small when it arrives, every derived size is small and the original on disk is small too.
Then I stopped WordPress generating sizes that nothing on the site uses. A filter on intermediate_image_sizes_advanced drops the 1536 and 2048 variants and two of the three theme sizes, leaving thumbnail and medium. Files per image went from ten to three. After that I regenerated the library and deleted the orphans, and the uploads folder went from 560 MB to about 20 MB, which is a smaller number than the theme.
Explicit width and height on every image, lazy loading on everything except the first illustration, and fetchpriority set high on that first one. None of that changed the weight at all and all of it changed how the page feels, because the layout stopped jumping around while images resolved.
Page caching came last, which surprised me, because caching is the first thing that gets suggested whenever this comes up. Docs pages change maybe twice a month, so the lifetime is set to a day and it purges on save. Warm time to first byte is now about 90 milliseconds. Cloudflare sits in front with a rule treating everything under the uploads path as immutable for a year, which is only safe because a changed illustration always gets a new filename. I also dropped one of the two webfonts and subset the other, which took the theme payload from about 500 KB to about 240 KB.
Where that leaves a tutorial page is roughly 550 KB total, of which 312 KB is the four illustrations at 78 KB each. Largest contentful paint 1.3 seconds on the same throttled profile.
The honest part is that the illustrations still cost real weight. A text only page on the same theme comes in around 240 KB. The guide character roughly doubles a page, and I chose that trade rather than got it for free, so I now cap it at four illustrations per page and never put one above the fold on an index page. If the tool were aimed at developers I would probably not have done it at all.
The bigger problem is not weight, it is drift. Regenerating the same character for a new page does not give back the same character. Same character, same notes, and the sleeve reads a different length, the fringe lands on the other side of the forehead, the green of the coat comes back slightly colder. On one page in isolation nobody would notice. Two pages open in adjacent tabs and it reads as a sibling. So I keep a folder of about sixty approved renders and reuse them rather than generating fresh, and when a page genuinely needs a pose that does not exist yet, I make a batch of eight and keep whichever is closest to the existing set rather than whichever is best on its own. Twice I have gone back and replaced an image on an older page because a newer one made the old one look wrong. Every image on the site is a still for the same reason, since I can hold a set together with stills and I have never managed it with anything that moves.
The guide character is AI generated. No illustrator drew it and no model posed for it. That is stated in the site footer and on the about page, and I would rather it sit there in my own words than turn up later as somebody's discovery.
Standardising the art was the other half of the fix and it is the half nobody writes about. There are five poses on the entire site and no others: pointing at something, holding something, sitting, arms folded, and looking at a screen. The character is always angled the same way, a fraction off centre. The crop is always from the knees up. The background is always transparent and never a scene, which means one file works on both the light and the dark theme without a second export. Everything is exported at exactly nine hundred pixels wide, so nothing on any page is at a different scale from anything on any other page.
Filenames carry the pose and the page slug with underscores, and the alt text gets written at the moment the file is made rather than in the editor at publish time. Those two habits are why the media library is navigable at all now. The old library was not unusable because it was large. It was unusable because it was anonymous.
The site itself is WordPress, the guide character gets drawn in APOB AI, and every image goes through ShortPixel before it ever reaches the media library.
The thing I would do differently from the start is decide the pose set before drawing anything, the same way a project settles its icon set before building screens. I generated on demand for the first six months and it produced about ninety illustrations, no two of which shared a crop, and most of those had to be remade from nothing once the rules existed. That rework cost more time than the entire performance exercise did.
Forty one tutorial pages are live and nine more are still drafts. The only check I run before publishing now is the size of the folder the images came out of, which takes about four seconds and would have saved me a fortnight if I had started doing it a year ago.
So exploring the new 7.1 stuff, and while more direct access to the patterns and such is nice, the confusing and concerning part is this new "design" option on the right when you first click the "edit site" and get options to move your template blocks around.
That design section seems to have some default new patterns that aren't part of the theme I'm testing with, and it's unclear if these would edit the core theme templates, or just provide another option?
I can't find any documentation on these, on either how to add to them or remove this entirely so some user doesn't torch the theme for all other uses on our multi-site instance.
Anyone found info on this?
I’ve started to notice that some of the biggest WordPress headaches usually come from small things that were ignored earlier.
For me, keeping plugins/themes updated, removing things that aren’t actually being used, and having regular backups has prevented a few problems from becoming much bigger ones.
I’m curious what it’s been for other WordPress users and developers.
What’s one WordPress habit or practice that has saved you from a major issue later on?
Hey, I’m very new to Wordpress and not very tech savvy. I have been trying to upload a pdf to my website without having this toolbar (in the red circle) visible. Been trying to find answers online to no avail. I don’t have Adobe which a lot of guides seemed to have.
Is this possible without plugins?
Thank you
WordPress does not include a chatbot in any version. There's no setting to switch on and no block to drop into a page. To add a chatbot to WordPress, you need a plugin.
If you heard that "WordPress has AI now," that's because back in May 2026, WordPress 7.0 added internal wiring to make it easier for plugin developers to build AI-powered features. But there are still no AI features out of the box, and the WordPress core team has no announced plan to add any.
This added wiring is not a chatbot. It will do nothing until a plugin puts it to use. So just like e-commerce, email marketing, or any other specialized feature, adding a chatbot to your WordPress site will still require an AI chatbot plugin.
Plenty of plugins compete to be the best WordPress chatbot. Most sit at one extreme or the other: free or low-priced plugins where you have to bring your own AI, or high-priced all-in-one help desk platforms that provide a lot more than the typical WordPress site needs. These can be good solutions for the right customer. The big question is how much of the AI system do you want to manage yourself.
These plugins are commonly marketed as "Bring Your Own Key" (BYOK), but "Bring Your Own AI" is more honest. They give you hooks into WordPress and a UI for customization. The rest is “batteries not included” and you supply everything that makes the plugin actually work.
You pick your AI vendor, the AI subscription plan, and the AI model. You generate the API key and configure its permissions to keep your account secure. And often you write the instructions that teach the AI how to provide customer service in the first place.
Bring Your Own AI plugins put you in the driver's seat. Every decision about your AI tech stack is yours — as well as every part of the configuration, maintenance, and cost. That's a lot of work to take on, but if you're a developer or have one on your team, that can be a fair tradeoff for total control.
These come at things from the opposite direction. For enterprise help desk platforms, customer support is their entire business, so they typically offer a fully managed service where you never have to think about what's going on under the hood. You pop an embed code onto your website, and your customer service department gets a ticketing system, live chat, a knowledge base waiting to be filled, and increasingly some kind of chatbot comes along for the ride.
These services may work with WordPress, but they're not made for WordPress. Support may be limited, and the connection to your actual content may be shallow or even require manual updates. The AI is often a secondary feature, and their pricing is built around agent seats, ticket volume, and add-ons, which can be overkill for a small business.
Help desk platforms provide a lot more than a chatbot. If your customer service department already lives in one of these for email and ticketing, having your AI assistant in that same inbox can make a lot of sense.
A customer support chatbot is more than a window into your website. When choosing the best AI chatbot for WordPress, its value depends on where it gets its information, how current that information is, how much work it requires from you, and what it really costs.
Installing a plugin is easy. What happens next matters more. Do you have to choose an AI provider? Create and configure an API key? Select a model? Write the AI your own instructions on how to be a customer service rep? Troubleshoot anything that goes wrong?
When you compare AI chatbot solutions, weigh what they promise to do for you against how much ongoing responsibility they leave to you. If you're not a developer, you may be happier with a managed solution than a BYOK one.
This one matters most. Newer chatbots use Retrieval Augmented Generation (RAG): they index your pages, posts, and product listings, and an AI model answers from what it finds.
Chatbots without RAG typically aren't even powered by AI; they're essentially automated phone systems with better typography. Customers have hated “Press 1 for Billing” for decades, and the web version is not much better.
Websites change constantly. You publish new pages, revise policies, update pricing, add products, discontinue old ones, and rewrite shipping and return information.
So when something changes, who makes sure the chatbot knows about it? Some require you to upload documents manually. Others scrape your site on a schedule. If a chatbot isn't hooked into live content updates, it's probably giving outdated answers.
With Bring Your Own AI plugins, the sticker price is never the whole story. The plugin may advertise a low one-time purchase price or may even be free, but that doesn't include the AI service. Every BYOK plugin relies on an AI provider that bills you per token used, so if you also paid for the plugin, now you're paying twice: once for the license, then every month for usage. And that second bill fluctuates. It rises and falls with your traffic and how visitors use your chatbot, making it difficult to predictably budget for.
BYOK plugins split the bill in two and hand you the unpredictable half. Help desk platforms fold AI chat into per-seat pricing designed for large teams. And with free plugins, when something breaks, getting support usually means posting to a forum thread and waiting for a volunteer to notice.
Don't just ask how much the plugin costs, instead ask yourself: "What am I paying for, who is responsible for making this work, and how much of that responsibility do I actually want?"
For a WooCommerce site, an AI chatbot can be useful for much more than generic support. Customers may ask about pricing, specifications, inventory, shipping, returns, sizing, compatibility, or other details spread across the website and product catalog. A useful chatbot can pull all of that together quickly and conversationally instead of making the customer hunt for it.
For most WordPress site owners, the requirements are pretty straightforward. You already have the information your customers need. It lives in your pages and posts, in your return policy and your product catalog. The challenge is getting it in front of your customers when they have a question.
You probably don't need more technology to manage. But you do need a system that understands your content, stays current as it changes, and answers your customer’s questions before they bounce.
In short, you need an AI chatbot that just works.
To learn more, read the original post on the JustAsk WP blog.
I’m doing some research on how WordPress freelancers and small agencies manage ongoing maintenance across multiple client sites.
I’m especially interested in people managing roughly 10+ WordPress sites, although anyone responsible for several client sites is welcome to participate.
I’m trying to understand things like:
I’m not trying to sell anything in the survey. I’m trying to understand how people actually handle this today before making assumptions about what should be built.
I put together a short 5–7 minute survey here:
https://forms.gle/H7mKPdzjCJLnHrv76
I’d also love to speak with a few freelancers or agency owners for a 20–30 minute conversation about their workflow.
If you manage multiple WordPress sites, your experience would be extremely useful — including if your current setup already works perfectly and you don’t see this as a problem.
Site getting 522 error. Down Detector showing active reports. https://downdetector.com/status/wp-engine/
I opened a support chat and it said I was 99 in the queue lol so I quickly closed that out.
When you're looking to purchase a Pro plugin for its paid features, how do you know it works for you?
Do you go by the feature list and docs, contact support with questions, buy it and refund it if it doesn't fit, or look for a way to test-drive the Pro version first? And if there's no way to try it, does that ever stop you from buying?
Im doing an article that i want to have detail drop downs so readers can click on it if they want to see the deails of something.
When i use only words and preview the detail drop downs show.
When i add in an HTML so i can add in a coded table and preview the detail stuff disappears.
I used to add tables from excel in the details drop down but i was trying to make the teams look nicer with HTML.
Any reason they disappear on the preview page?
The Above is what it looks like when i edit but nothing shows after i save draft and then preview.
I'm thinking of getting elementor one and using it across all my new site builds. Do any of you have this? Whats you're experience with it? Is the AI generated code good, jenky, doesnt work at all. From the video the ai powered widget creation looks amazing. Would love any thoughts here.
I think it would be nice in the next update if you validated this css:
Login![[link]](https://i.redd.it/w7t7q8mquxmh1.jpeg){kind=link}
![[link]](https://i.redd.it/gwaxjjcebxmh1.png){kind=link}
/wp-includes/blocks/image/style.min.css This has been making me nervous for a few weeks now on the websites I audit.
Thank you all
With AI tools like Claude, Codex, Cursor, etc. becoming so common, I’m curious what actual WP developers are doing these days.
Are you still using Elementor/Bricks/Divi, or moving toward custom themes, templates, Gutenberg blocks + ACF?
And how much has AI changed your workflow?
Would love to hear your actual stack and type of projects you work on.
