Home User profile
tagDiv Member
This user did not write anything. So we are just showing here some random text to make the profile page look nice :)
sgaddo
tagDiv Member

Thanks Simion.

I created a new temporary admin user and sent the credentials to your mail.

Waiting for your reply.

sgaddo
tagDiv Member

Hi Simion and thanks for your reply.

But in older theme versions this system was not yet implemented I believe, like the version you are using on the main website.

Actually, as I mentioned, the two sites are running the same older theme version…that’s why I was wondering how come they are behaving so differently, even in the HTML code loading the pics.

Also, I’m totally sure that nobody changed anything in the settings nor disconnected the account from the LIVE env site (before the issue happened). Anyways I did again the connection with the Instagram profile, but this didn’t make it work.
Furthermore, reading other users comments it seems that updating the theme would not solve the problem.

So basically, known that they’re running the same theme versions, why the LIVE site is loading pics from remote (forbidden) URL and the DEV one is loading them from local directory, and apparently working ok?

(I wrote “apparently” because maybe we should try to post a new pic on the Instagram profile, to check if the DEV website will load it correctly).

sgaddo
tagDiv Member

Hi support team.
I have the same problem, the Instagram image feed is not showing the pictures in the global footer, but I wanted to point your attention on another aspect:
I have exactly the same site, running the same version of the theme (10.4 and I cannot update), in two different environments: production (or LIVE) and development.
The production environment doesn’t show the feed and, looking at the code, it’s trying to load the pictures from this URL:
https://scontent.cdninstagram.com/v/t51.2885-15/274622029_3149200718694712_2486979673539822313_n.webp?stp=c227.0.500.500a_dst-jpg_e35&_nc_ht=scontent.cdninstagram.com&_nc_ohc=nAgJL-Z6sTQAX9DZc0g&edm=ABfd0MgBAAAA&ccb=7-5&oh=00_AT9Vtjo_bZwJkSNxjeqa5R9Vl8bOjeANNHqZbb8KhDs0iA&oe=62C5ABE4&_nc_sid=7bff83

And if you go on that URL the browser shows URL signature expired message.

In the development environment instead, the instagram feed is showing the recent thumbnails, but they are loaded locally (so from the local /wp-content/uploads/2022/04/ directory) and as a link background.

That’s a completely different way of loading and showing pics. Why?
And why it’s still working on DEV?

The websites are:
https://www.worldfootballscouting.com/
and
https://dev.worldfootballscouting.com/

So, I hope this will help your developers to give us all an answer.
Waiting for your kind reply.
Thanks.

  • This reply was modified 3 years by sgaddo. Reason: The pasted code example was not showing properly
sgaddo
tagDiv Member

Yeah I know that Lucian, I just tried to make it feel easier than it seemed =)

Hope everybody solved.

sgaddo
tagDiv Member

I also had same problems: the site css settings were lost and in theme panel almost nothing was editable anymore…
“Theme colors” was working and I noticed that the colors were those I set and not defaluts, so i just saved settings without changing anything and it came back as it was before.
Regarding the unusable panels I just hard refreshed my browser (ctrl+f5) and it worked.

Hope this helps!

…and I gotta say I scared to death during those endless minutes…

sgaddo
tagDiv Member

Hmmmmm…so, to avoid unexpected behaviors, instead of importing the whole js_composer.css file, I could just extract all the classes that I need (such as the buttons and the “call to action” button) and style them as I like (which sounds like a normal css override =) ).

Thanks to you Lucian, you all are very kind.

sgaddo
tagDiv Member

@reenamm
I just solved in this way, but I’d like to know from TagDiv’s crew if it’s ok:
in my child theme’s custom css, I’m importing the right css from Visual Composer’s assets folder, in this way:
@import url("../../plugins/js_composer/assets/css/js_composer.css");
Look at my page now
http://mailneo.biz/about-neomobile/

Why doesn’t the theme load it by itself?

sgaddo
tagDiv Member

Hi Lucian,
nothing we talked about solves the problem in my case =(
I have:

  • Theme Version 4.3
  • Visual Composer Version 4.3.4 (deactivated, uninstalled and reinstalled several times from your package)
  • Child theme running (I also tried to activate the main theme)
  • I deactivated all plugins and tried again but it doesn’t work

Anyways, in your screenshot http://screencast.com/t/h8547NHbMdVa Button 2 is not stylized like Visual Composer edit page does, but they come out both with your own style. Instead I’d like to have both different styles, Visual Composer’s and yours.
In your example what should be the actual difference between “Button” and “Button 2”?

Thanks!

sgaddo
tagDiv Member

Ciao Lucian!
I will try your solution as soon as I can.
Do you think that happened maybe because I’m running the child theme?

sgaddo
tagDiv Member

Hi Lucian,
here’s what I see in edit page with Visual Composer
http://www.screencast.com/t/w0gQLdhOtNs
The upper two are made with “Button 2” element while the second on the right side is made with “Button” element.

On this link there’s my page
http://mailneo.biz/about-neomobile/

Below the video you can see links instead of buttons, but the second red one is styled as your tagDiv buttons.

Thanks!

sgaddo
tagDiv Member

After the last update I have the same problem as Novaque’s.
All the buttons (button 2 in Visual Composer) in my pages were well stylized. Now they appear just like common links.
But in page editor they are always styled like i set in the VC options.

I also checked that in visual composers css, the code to get them good looking is still there.
How can I reactivate it?
But above all, how come did you disabled it?

Thanks guys!

sgaddo
tagDiv Member

Just like you said, I replaced the original file and it worked!
I don’t know why I was editing td_data_source.php file from an old version, in which the variable name was different… -_-

Thanks Lucian!

sgaddo
tagDiv Member

URGENT
I had the same need about sticky posts, so I changed to 0 this parameter

$wp_query_args = array(
    'ignore_sticky_posts' => 1
);

but now I get the following error on every single page
Fatal error: Access to undeclared static property: td_unique_posts::$show_only_unique in /htdocs/public/www/wp-content/themes/Newspaper/includes/wp_booster/td_data_source.php
and the site crashes!

Obviously I tried to set the parameter back to 1 but still getting the same error!!!
I also tried to change the “Unique articles” setting…nothing…

HEEEELP!
The site is unusable!!

sgaddo
tagDiv Member

No problem Lucian!
I guess yours will be the quickest and painless way to get it =)

Thanks to you!

sgaddo
tagDiv Member

Don’t consider my EDIT. It doesn’t work, because of different path structure…

  • This reply was modified 11 years by sgaddo.
sgaddo
tagDiv Member

Same wish here =)
The file responsible for social icons order is td_social_icons.php located in
wp-content\themes\Newspaper\includes\wp_booster
Changing the order of array items we can get our custom order for every social widget using those items.
Of course we will lose everything at the next update =(

My question: is it possible to load custom class within child theme without redeclare it?

Thanks a lot for your great job tagDiv guys!

EDIT
My temporary solution is changing the way in which td_social_icons.php is loaded by td_wordpres_booster.php, using locate_template function (already used to load custom child modules) instead of require_once and then and using my own td_social_icons.php in child theme (of course creating wp_booster folder in child theme)

Of course is temporary because at the next update I will lose the changes as well, but in this way at least I will keep my own social sorting =)

sgaddo
tagDiv Member

Hi Lucian and thanks for your answer!
I was already trying to do something in there, but “Top right (social)” widget area was already empty!

So I solved putting some random widget in that “Top right (social)” and then deleting it right after.

But now I’m wondering: how come this behavior came out only when I activated the child theme? With the main theme everything was just fine… =)

sgaddo
tagDiv Member

A brand new version (4.2) was just released…
I just updated, both the theme and the child theme, but it happens anyways =(

Viewing 18 posts - 1 through 18 (of 18 total)