Custom Post Info Lines section missing in Weaver Xtreme Plus 7.0

[Weaver]

@gr8fl, @casey. Should be unblocked now. I don’t know how you got autoblocked.

I really don’t know for sure how that happened. Akismet perhaps?

[casey]

Yes, this was a Weaver Xtreme Plus option, not something in the post editor.

The option showed up here:

Appearance → Weaver Xtreme Admin → Main Options → Post Specifics

At the top of that Post Specifics page, there is a row of hyperlink shortcuts to the different sections on the page. The last one listed is:

Custom Post Info Lines

That link is still visible at the top of the Post Specifics page, but the actual Custom Post Info Lines section no longer appears anywhere on the page. When I scroll through the page now, the last section I can find is More Post Related Options.

What I had done years ago was use Post Meta Info Areas to hide the standard/default top post info output, and then under Custom Post Info Lines I inserted my own custom line for what I wanted displayed instead.

The custom line was:

<code class="language-html">Posted on %month% %day%, %year%

That is what produced the small plain “Posted on…” line under the post title.

Hattie’s Garden is still doing this correctly. I can see it on the front end, I can confirm it with Inspect, and I can see the settings in the exported .wxb file. In the Hattie .wxb file, the settings custom_posted_on and custom_posted_on_single are present, with the custom “Posted on…” line.

IMC-Lewes stopped doing this. On the front end, there was a blank space where the custom top post info line used to be. When I inspected the affected page, Weaver was still outputting the entry-meta container, but it was empty:

<code class="language-html">

And when I exported the IMC-Lewes .wxb file, custom_posted_on and custom_posted_on_single were not present.

So the difference is:

Hattie’s Garden still has the old Custom Post Info Lines settings in the .wxb file and still displays the custom line.

IMC-Lewes no longer has those settings in the .wxb file and was outputting an empty entry-meta container.

My temporary workaround on IMC-Lewes was to uncheck Hide Post Date under:

Main Options → Post Specifics → Post Meta Info Areas

That made Weaver output the default post date again. Then I used CSS to make that default output look more like my old custom line by hiding the calendar icon, adjusting the font/weight/color, and adding “Posted on” before the date.

But that is only a workaround. What I really need is access again to the actual Custom Post Info Lines section so I can restore/edit the top post info line directly instead of approximating it with the default post date plus CSS.

Both sites are using WP 6.9.4 and Weaver Xtreme Plus 7.0. I will update to 7.03 and see what happens.

[Weaver]

This reply has been accepted as the best answer.

It is fixed as far as I can tell. get the plus 7.0.3 version

[GR8FL]

>> @weaver:

Should be unblocked now. I don’t know how you got autoblocked.

I really don’t know for sure how that happened. Akismet perhaps?<<

 

I am back. Thank you for unblocking me. I think we’re inadvertently relying on too much AI and the SPAM BOT got triggered somehow. I will update to 7.03 on my sandbox site (that unfortunately got updated to WP 7.0).

Question: How do I see the actual editor instead of the visual? I would like to actually see the html here. That option used to exist… a long while ago.

[Weaver]

Question: How do I see the actual editor instead of the visual? I would like to actually see the html here. That option used to exist… a long while ago.

---

Don’t really understand this question. editor vs visual? where, when?

I’ve not had difficulties with WP 7.0 othere than adjusting to some of the more subtle interface changes. I think the biggest issue is breaking plugins with dependencies on old PHP 7.2 and before. But there are legitimate security issues behind that decision I think. As I noted in another post, this forum used to have a very nice way to show a bar before posts you had read. That pluigin from 2014 broke. I tried to fix it, but to no avail. So, that is the biggest drawback.

My hosting company, SiteGround, forced update all sites to WP 7.0. Part of that, I think, is some of the new AI support now built into WP. SiteGround now has this automatic AI inteface popup from the Admin pages that actually looks like it could be useful. It seems to know how to directly interface with WP core, and help design and change settings by using human language inputs. So I guess we’re being dragged into AI whether we like it or not.

I will be out of the office for a few days with limited internet access.

[GR8FL]

Quick update: I’ve installed Weaver Xtreme Plus 7.0.3 on my sandbox site and removed the temporary CSS workaround I had added for the top post info line/calendar icon issue.

So far, 7.0.3 appears to have fixed the problem. The Custom Post Info Lines section is visible again, and entering the following in both Top Post Info Line and Top Post Info Line (Single) restored the display correctly:

Posted on %month% %day%, %year%

One interesting thing: on the IMC-Lewes sandbox site, those fields were blank, so I had to re-enter the custom line manually. I’ve also tested Hattie’s Garden and updated the production side there, and that looks fine as well. For now, I’m leaving the IMC-Lewes production site alone since that one involves a little more surgery, but 7.0.3 does seem to have resolved the issue.

[GR8FL]

I still am using SiteGround and have no issues with them. Regarding the auto updates, I set it up a long time ago, despite their repeated warnings, to turn off auto updates on any plugin or core updates. They complied with my request.

My sandbox site does have auto updates and it did come with AI Agent by SiteGround that they describe as “Do more and faster site maintenance, updates, content, SEO and more WordPress tasks – on one or multiple sites – through a simple chat.” I disabled it for now until I have more time to understand it. I am not against AI, just want to know more before I enable it. Perhaps it will be useful.

[Author]

Posts