[creatorofstuff]

No, I have not done anything at all. I do not know why it did not show up on the wish list page. As you can see in the screenshot, it seems to be there now. And it is not lined up.

As I mentioned above, I created a completely new child theme in order to get rid of all of the fixes and bandaids I was required to use in order to make the theme work the way it is supposed to work. I really do not want to have to add code to my theme in order to make things line up. It seems like they should line up by default.

If there is something I have done to cause this, please tell me. I can’t imagine what it could be, but I’d rather fix that then add more bandaids.

This is the only code that has been added (which you told me to add to fix things) that I don’t completely understand. Is this causing it?

.post-1333 .alt-three.full-width-text:after {
display:none!important;
}
/***to prevent right sidebar from dropping down on post page***/
.single-post .sidebar.right-sidebar {
margin: 0px !important; float: right;

Thank you…

Attachments:

You must be logged in to view attached files.

[creatorofstuff]

The site is up again. Would you mind having a look again? Thank you.

[creatorofstuff]

Sorry about that. I’m having a hard day. My site is down. 🙁 I’m hoping it will be up as soon as possible.

Do you want me to reply to this when I know it is back up?

[creatorofstuff]

Oh gosh, I just realized the grammar in the first sentence is wrong, too! Yikes!

[creatorofstuff]

Never mind. I figured it out, finally. In case anyone else is searching on this, it’s:

.testimonial-text {…name of font, etc….}

[creatorofstuff]

Good point.

Thank you once again!
🙂

[creatorofstuff]

Hi David – No, I had not done anything at all! I was waiting to see what you had to say. But I just checked it and you are right! It is now working. I can’t even imagine what changed to make that happen. Little gremlins, perhaps? Very strange, indeed.

I apologize for the false alarm. I will try updating the theme on my live site and cross my fingers that everything works properly…

Thank you!!!

[creatorofstuff]

Did you notice in my original comment that I said “I have not been able to get it to work at all in subsequent attempts to view”?

This is part of the problem (it just spins and never loads), and I don’t know what is happening. The only difference is that I updated to the theme 3.12 and then this problem started.

🙁

[creatorofstuff]

Thank you! 🙂 🙂 🙂

[creatorofstuff]

Thanks Rui,
1. As for using a WordPress hook, if I’m understanding this right, wouldn’t I then be editing a WordPress file that would be overwritten upon updates? I think I need to spend some more time learning about this. It’s confusing.

2. Thank you. I do see now what was happening. I missed the % mark, and somehow read it as pixels! Sorry for your trouble!! :}

[creatorofstuff]

This reply has been marked as private.

[creatorofstuff]

Yes, I am using a child theme. I have not touched the theme files.

I did the update through the admin panel. It looked like the screenshot. That’s when weird things happened.

Attachments:

You must be logged in to view attached files.

[creatorofstuff]

I’m a bit confused. (Oh, and it’s all one page, by the way. I was just showing sections of that page.) When I logged in to edit the page, it was already in the page builder mode, which is where I left it when I built the page in the first place.

I may have made some edits in the “classic” mode, which I have had to do once in awhile through the site in a few places but for the most part, I always use the page builder. I certainly prefer the page builder!

But just for fun I went ahead and hit “update” in case that might help, but unfortunately, it stayed the same.

Anything else I need to try?

????

See screenshot…

Attachments:

You must be logged in to view attached files.

[creatorofstuff]

This reply has been marked as private.

[creatorofstuff]

Thank you, David,

I can see why you would make improvements that might affect legacy versions of the theme.

Perhaps it would save both you and your customers a load of headaches if you would create a dedicated page of fixes for those things on your support form.

For example, “if the update causes your full width text block to change, apply this code: …….”

If you already know people are going to have these problems, it would be helpful. Because it creates extra work for you, and it means we (the customers) have to create a post, then wait for the answer before we can fix the problem (if we aren’t good coders like me).

Thanks so much – I do appreciate the support!