Skip to content

Details

When you take over a website that someone else built, it's a good idea to review the current setup thoroughly--BEFORE you agree to take a project on, and certainly before you quote a price for what seems like a simple fix.

Sometimes things really are straightforward, and the original developer set things up in a way that makes sense and accords with best practices for WordPress development (such as they are).

But sometimes you do a code review and wonder "What were they THINKING?"

Come share your best practices for what to do next when you discover code chaos and the client DOESN'T want to rebuilt the site from scratch. How do you break the news? How do you decide what to do next? What are some things you can improve without having to do a rebuild?

Tell us about the craziest thing you ever encountered when you took over a website--and what you did to fix it.

Sponsors

Sponsor logo
Bluehost
Bluehost makes building, growing, and managing WordPress websites easy!
Sponsor logo
Woo
Woo is the leading open-source ecommerce platform, built on WordPress.
Sponsor logo
hosting com
Global hosting, community roots, built for what’s next
Sponsor logo
Jetpack
Safer, faster WordPress.
Sponsor logo
WordPress com
We're a hosted version of the open-source software
Sponsor logo
Kinsta
Build with WordPress, grow with Kinsta.
Sponsor logo
Page.ly
Pagely provides hosting for our new EastBayWP.com site
Sponsor logo
Tech Liminal
TechLiminal provides our awesome meeting space
Sponsor logo
A2 Hosting
A2 Hosting has kindly offered to pay for our pizza on an ongoing basis.
Sponsor logo
Modern Tribe
Modern Tribe is providing pizza and swag for the July 2015 Meetup.
Sponsor logo
Playwire
Members get upgraded to second tier of pricing .75 per gig of bandwidth
Sponsor logo
O'Reilly Media
Discount codes for O'Reilly books, e-books, training.

Members are also interested in