Scott Reilly

Hi @balvan64,

In order to troubleshoot this, we should first determine if there is a plugin-level conflict, or if the CSS you defined using the plugin is preventing things from being shown.

So firstly, activate the Add Admin CSS plugin and go into its settings and delete anything that you’ve configured. (Create a copy of the CSS you may have provided if you want to add those back in later.) No CSS files should be linked and the “Admin CSS” field should be empty. Save those changes and try to access the WPML translation interface. Does it load? If not, then there is a plugin-level conflict that is out of your hands. Let me know if this is the case, and if you happen to have any error log entries from when you tried to access the WPML translation interface that may report any errors. (If none of that makes sense to you, simply report back that your issue was just from activating the plugin.)

If the WPML translation interface loaded after you’ve activated the Add Admin CSS plugin and cleared its settings, then the conflict is probably with the CSS you defined. I’d reintroduce CSS in chunks or rule by rule, each time saving the changes and reloading the WPML translation interface page to see when it stops appearing. Hopefully you eventually introduce CSS that causes the issue, so you’ll know what it is and can change/omit it.

If you are unfamiliar with CSS or don’t understand what I’m suggesting, feel free to say so but please provide a copy of the CSS you configured with the plugin and I can try to debug the problem.

Hi @prestonwordsworth. I think you may be misattributing behavior to the Disable Search plugin (or I’ll need more details). Other than hiding or disabling search forms/widgets/blocks, the only other thing the plugin does is set a 404 response for any attempted search. It does not perform redirects nor issue 301/303 response codes.

@doffine: Thanks for inquiring! Fear not, the Disable Search plugin has not been abandoned! I just released v2.0.1 of the plugin to note compatibility through the most current version of WordPress (6.3.1). There have not been any reported issues or bugs since the previous reason.

Hi @emgb_520: The Remember Me Controls plugin hasn’t been abandoned, though it had been awhile since an update. I have just released v2.0 (now v2.0.1) of the plugin which improves the plugin settings page and confirms compatibility through with WordPress 6.2+. Cheers!

Hi @moshe1111: Unfortunately, what you’re looking for isn’t something the plugin is written to do. It can only replace specific text with other specific text.

It does not identify text by general criteria (e.g. “a paragraph with less than 10 words”) and it can’t replace any of the original text back into itself (e.g. putting text that got found back into the post but now within certain tags).

If you know the text of what you’d like to be put into H2 tags, you can use the plugin and explicitly list them, (e.g. Daily Overview => <h2>Daily Overview</h2>). But it is not a feasible approach if there are a bunch of different phrases that you need put into H2 tags, or if the phrases also appear within normal text.

Thanks for the report, @afrikane! I’ve just released v4.0.1 of the Blog Time plugin which fixes this issue.

Cheers!

@americanfreak: Just a follow-up on this…

The Blog Time plugin has just been updated to v4.0. It introduces a setting (found at Settings -> General) for easily configuring the blog time format. It also introduces support for the ‘T’ timezone format token, which is used for showing the timezone abbreviation (e.g. “PDT”).

Cheers!

@azureconcept: Glad you found the time formatting you needed!

Admittedly, the current version of the plugin does not make it easy to customize the time format — it can only be done using a filter in custom code.

However, I am finishing up the next version of the plugin which will add a setting for customizing the time format. I’ll follow-up here to let you know when it releases, if you’re interested.