As mentioned in my first post, I’m using Elegant Themes‘ Divi and the Divi Builder, which is a brand new experience offering many new challenges. As predicted, I broke the blog on Wednesday, but was traveling. I could not fix it and threw caution to the wind: I asked for help.
Back in 2012, I won a Lifetime Membership to Elegant Themes. I loved their cleanly coded, easy to use, easy to customize themes. I moved away from those in 2016, mainly because they appeared to be phasing out all the themes I loved and going all in on their theme and builder combination they called, “Divi,” which I had tried and, frankly, hated. I paid for a different premium theme, called “Fullby,” which I loved, but chose to move away from for two reasons: The developer was not responsive to support requests, and I could see that it was not likely to keep up with the inevitable changes to WordPress–namely, the dreaded Gutenberg block editor. Divi was before its time. I fought that block editor as long as I could, while some raved about how wonderful it was and others wrote plug-ins to disable it and restore lost features of a bygone era. Mainly, I fought it because it did not allow for the easy fine-tuning of alignment between text and graphics. I was ready to hand-code each post in HTML if I had to, just to get those elements to align.
And then I thought, “Fine, I have a Lifetime membership to Elegant Themes, and it seems a shame to waste it. Let’s give Divi another go. I have vacation, plenty of time to waste. I can do this.”
I am grudgingly ready to admit that Divi and I are starting, mostly, to get along. I still half expect it to eat my posts (the main reason I despised it, early on, was that I’d tried it – then switched to a different theme – then switched back, and all my posts were gone).
But this weekend, I broke my blog. I entered a plea for help in Elegant Themes’ chat support. And waited. Nothing happened. I went to bed. In the morning, I had a lovely email from Abd, asking me to enable the support and admin features of Divi. At first I balked: Give someone else admin privileges on my blog? I don’t think so…
Then, “Why not? What are they going to do, delete it?” There was nothing here to delete. There are no members but me, and admin me has access to pretty much nothing. So I enabled Support and Admin privileges. Next thing I know, Abd and Vojin from Elegant Themes had gone to work fixing my world.
At first, I thought I broke my blog, but the real problem was not my messing around in the style.css file, trying to change the color of elements not accessible via the Customizer. The real problem was another plug-in.
Instead of the usual, “It’s some crappy plug-in you’re using. Disable them all, then re-enable one at a time to figure it out on your own,” they told me what was wrong and they wrote some code in the Divi theme to work around it. I didn’t have to disable the crappy plug-in. Sweeet!
Then, I asked Vojin how to change the color of the elements I was trying to change. He asked me what color I wanted. I explained that I’d rather understand what I needed to do–that I wanted him to teach me how to fish, not throw me a mackerel and feed me for a day. He got it, and did both, providing a little snippet of .css code to do what I’d wanted.
So now I am back to being a huge fan of Elegant Themes–yes, and Divi–because of their expert and kind support staff. It usually does come down to the people, doesn’t it? I’m willing to put up with a little technical annoyance if the support staff goes above and beyond. It’s why I’ve been a T-Mobile customer since back before their coverage was better than AT&T’s, and why I’ve stayed with them for nearly a decade. And now it’s why I recommend Elegant Themes’ Lifetime Membership, as well.
Oh, and the more I work with Divi, the less “technical annoyance” I’m encountering. It’s just a very different way of working. And now I know that if I get stuck, I am not stuck without the help of some very kind and knowledgeable people.