maybe be more specific. good luck!

i believe you request that through themeforest where you bought it

( i dont work here )

most wordpress themes you set featured image in post editor then template supporting that inserts it. for templates with blank image spot you manually insert image in post where desired

Weird it looks totally fine in td-composer view. I may just try to use a single image and retire the slider vs messing with it, so i can move on 🙂

Had changed the text to h2 from h3, tried changing back, but still breaks into the spacer area.

Looks like it is there, just loading bottom of page. Might be some table or div wrapping it breaking the layout?
(I don’t work here.)

How would I apply a fix only to the slider CSS itself and nothing else?
I have not tried anything like

.slide-meta h2 entry-title td-module-title {blah blah}

Hi
I always do manual ftp installs – I’m old skool 🙂

Thanks. I had renamed folder in past as old security practice, so thought maybe good idea to keep doing so as not been hacked, while using newsmag since first launch.

Peace out 🙂

Go in WP to posts > categories and hover mouse over the category name and you should see the ID as part of the URL.

There are instructions on here, somewhere, on how to scrub your database, which you need to do before reinstalling the latest theme *and* the latest td-composer plugin. There was a defect in some code used by *many* themes and plugins in the wild that allowed an injection. However, you need to clean that out of the dbase before anything else.

Once cleaned, consider installing WordFence, at the very least; and do security hardening in htaccess file to disable access to common WP files hackers try to attack. Disable XLMRPC, etc.

See this topic for Newspaper theme — note, this is only for the common wp-zexit hack, not any other issue you have from insecure or nulled third party plugins:

https://forum.tagdiv.com/topic/wp-zexit-malware-and-newspaper-theme-problem-please-see/

(I don’t work here.)

• This reply was modified 2 years by simchris.

FYI:
Error 1011 Ray ID: 887e1726fead7c55 • 2024-05-22 16:12:54 UTC
Access denied
What happened?
The owner of this website (magazine.pagesjaunes.online) does not allow hotlinking to that resource (/wp-content/uploads/2024/05/Jeune-Afrique-.png).

Couple quick notes on “being prepared” when doing updates to Theme:
a) you should make manual backups of your dbase via hosting panel, AND via the WordPress ‘export’ function prior to any updates, including WordPress core – theme does not manage that for you; no theme does
b) you should put some custom code in the WordPress > Appearance > Customiser when possible as this lives outside theme, so will not die with a broken update
c) you should copy paste custom code for widgets, footer elements, and CSS into separate text file for ease of rebuild when an error
d) you should make a ‘map’ of your custom home page elements, such as rows and modules and settings for each (e.g., category ID, skip IDs, etc)

Just some feedback for newer WordPress users. This kind of planning will really save you from going nuts if there is hiccup during any update of anything.

🙂 Chris

(I don’t work here; WP user since 2004.)

I ran into issues with change to javascript stuff in WordPress. Clearing your browser cache completely, like hard reload in Chrome, solved some stuff for me.

do you see the twitter tags in the meta of your header, when viewing page source? also, remember twitter.com just switched to x.com, so might be some weirdness. and twitter does not always capture any meta if their connection to your site times out.

Are the images placed into posts as webp?
If you open up a post, and look at the editor, are the images listed as .webp or .jpg ?

omit the code code at atart/end of course 🙂

I think this is the code we use; put in the WordPress > apperance > customizer ; not in the theme panel

<code>
@media(min-width:1021px){.td-footer-container,.td-sub-footer-container.td-container{width:100%}.td-footer-container.td-container .td-pb-row,.td-sub-footer-container .td-pb-row{width:1021px;margin-left:auto;margin-right:auto}}@media(min-width:768px) and (max-width:1021px){.td-footer-container,.td-footer-container.td-container .td-pb-row,.td-sub-footer-container .td-pb-row{width:756px;margin-left:auto;margin-right:auto}.td-footer-container,.td-sub-footer-container.td-container{width:100%}}
</code>

• This reply was modified 2 years by simchris.
• This reply was modified 2 years by simchris.

might be amount of ram allocated to php?

never seen this on my own site…did you try clearing browser cache? check site with malware scanner?

i thought you request refund where you bought it on themeforest?

a) you should make backup site
b) you should update theme and plugins to latest version
c) you need to do search/replace in your database for the redirect code — simply updating theme/plugin won’t fix it

You can simply download the ‘all files’ from your themeforest account. The plugin is in there. Just FTP it to your site (after making backup). Remember the NEW plugin might not be fully compatible with really ooooold theme.

There is a guide on here someplace.
(Sorry, I don’t work here.)

We had this issue on couple of websites after recent WordPress and PHP updates. Simple fix was to go and resave the footer and menu settings. It impacted Chrome on Windows 11, iPad, etc. Clearing Chrome cache didn’t help. Not just this theme, but an old WOO theme also.

Might be the javascript bug from latest versions of WordPress. If using Chrome due hard reload of page (force clear cache). This caused similar issues for me. Might not be issue, but worth a try. 🙂

Ads may not display on staging site unless submitted and approved to the adsense system as it’s not a live site indexed by Google.

what plugin ate you using for sitemap? if using Yoast you might need to go into settings and toggle sitemap option off then back on.

I DONT WORK HERE

I didn’t think you could use both editors same time? Maybe that is just my setup. I know we ran into a few issues with the bleeding edge PHP 8.x. I think 8.2x was as far as we could go. PHP 8.3 didn’t work for a *lot* of things. The TagDiv composer works fine with latest version of WordPress.

There was kind of a bug in WordPress admin, which required you to hard clear your browser cache due to a change in the internal version of jquery/javascript. I had issues where I could not set push date on posts. Clearing browser cache and hard clear via console in Chrome fixed that.

I don’t work here 🙂