Thanks, but why does Newspaper have those capabilities while Newsmag does not?

Converting to using tagDiv composer has been painful at best and now I have to add additional plugins for basic functions like tabs, which in a previous forum from 2 years ago you said was “in the works”.

For some reason you feel it’s more critical to add COVID-19 widgets than basic functions like buttons, tabs and accordions.

I don’t get it.

also i’m not getting any multipurpose shortcodes in my elements: buttons, icons, hero, etc.

https://tagdiv.com/tagdiv-composer-multipurpose-elements/

i disabled all of my plugins except tagDiv composer

I was able to migrate my customizations to the footer in a child theme by moving all of the customizations to /footer.php and disabling the footer in the theme panel.

When I tried to do the same with the header..no love. I even experimented with deleting the file in /parts/header one by one and they and no effect.

So I did what was suggested and tried to build the header in tagDiv Cloud library.

WHAT A NIGHTMARE!

I’ve been working a lot with ELEMENTOR lately which is pretty much drag and drop with granular control over everything you do.

To get things the way I wanted, requires extensive CSS manipulation (there are only limited options for creating columns) and worse when I tried to create the mobile version of the header, I started getting a barrage of error messages, which ended up nuking the whole template (hours of work lost) which I now have to go in and recreate and hope it doesn’t happen again.

If you want your big plan was to “require the use the tagDiv Cloud Library” then maybe you should have made sure that it was up to the task before this release.

And oh by the way, how the heck do I migrate from my staging site, to the live site. I don’t see any way to export anything from the library. Since your initial post said to use a staging site first to test, then what accommodations did you make for getting the template from point A to point B?

• This reply was modified 7 years by pmats777.

sorry, but creating a header with the tagDiv Composer is a nightmare, especially compared to Elementor. For one you can’t set the column percentages individually, there are only a limited number of choices. Then everything has some padding in it by default, so I have to go into every element and either code is via css because setting the padding and margin within the interface does nothing.

and worse the whole thing is buggy as hell. I spent hours creating a header then when I went to create the mobile version, it kept giving me error messages. Now when I open the file, it says that it the content wasn’t created in tagDiv Composer, and the column to add content to the mobile header has disappeared. So now I have to recreate the whole thing again, on top of which I don’t see anyway to export this to my live site, so I’m going to have to recreate it a third time (or more depending on how many more bugs I run into while recreating it).

@Calin

Thank you for your understanding?

Sorry but doesn’t seem to be too much “understanding” here when you implement this type of change that has major implications and use Envato as the fall guy.

IMHO what you should do is continue to support the current 9.6.1 (which currently has a cross scripting vulnerability) and release 9.7.x as a new theme or some other option to allow those of us who are using the theme not strictly “out of the box” to continue to use it without having to spend many hours or ask our clients to expend hundreds if not thousands of dollars to continue using a theme, that we recommended to them and now look like chumps for having done so.

That being said Envato’s documentation which you choose to use as cover also states

“To reduce the chance of users being negatively affected if they do not install/update the plugin, themes may choose to include a fallback until 30 November 2019. This is not compulsory.”

Well that doesn’t help whatsoever. My changes are already being tested in a staging environment. As noted in @raqys response you should have been prepared with some documentation of how to migrate if using a child theme, not just “use a testing environment”.

what files specifically address the exploits, without having to update to 9.7? Because of the way that 9.7 is structured it nukes all of the customizations that are in my child theme.

https://forum.tagdiv.com/topic/child-theme-and-9-7/

also, in the last version of 9.6.1 there is a directory labeled patch_9.6_9.6.1. what are those for and do those need to be uploaded separately to overwrite what is already in the existing Newspaper directory?

• This reply was modified 7 years by pmats777.

disregard. i found the solution:

When editing a post, there is a setting under Post Settings to specify the Primary Category (not to be confused with where you specify the Category in the WP interface).

Thanks.

Might consider adding that to your documentation, at least that there are big differences in setting options between Grid options.

.td-grid-style-1.td-hover-1 .td-big-grid-post:hover .td-module-thumb .entry-thumb {
transform: scale3d(1.0, 1.0, 0);
-webkit-transform: scale3d(1.0, 1.0, 1);
-moz-transform: scale3d(1.0, 1.0, 1) rotate(0.00deg);
}
/*GET RID OF HOVER EFFECT ON BIG IMAGES*/
.td-grid-style-1.td-hover-1 .td-module-thumb a:last-child:before {
background-color: rgba(0,0,0,0.01) !important;
transition: background-color 99.9s ease !important;
-webkit-transition: background-color 99.9s ease;
-moz-transition: background-color 99.9s ease;
-o-transition: background-color 99.9s ease;
}

that doesn’t really do anything, and in fact is worse.

Flex Grid 2 has the zoom effect in Safari as well. I’m trying to get rid of any rollover effect. Isn’t there a way to disable it using CSS?

thanks

Would also like to know how to disable the opacity change as well in case my client changes their mind.

Thanks.

i was able to get it to work by using an html / shortcode plugin, entering the code into the plugin and using the shortcode that was generated.

as i said in my post, i already did that and the version of visual composer that i just downloaded is 4.6.2.

do you not supply upgrades to 4.7.1 at this time?

if not, is there a fix to trying to get the fb plugin to display on the page?

i think i may have it solved. i had to force it to php 5.4

is that normally a requirement?

yes. i increased it to 128mb

hi

anything going on with this? i need to get this resolved before the weekend.

thanks

i sent you the login information via e-mail.

here is the final analysis from my web host:

This definitely appears to be theme related problem so you might want to contact the author of this theme and consult with him for more information on how to fix this properly.

this is the analysis from my web host who i had replicate the error

—————————

We have checked this for you and determined that your site may be reaching the maximum requests limitation on the server when using this specific theme.

This is very often caused by improperly coded scripts which run requests in a recursive manner filling all available slots. Usually the developers should be able to look into this and rectify the problematic code.

However, I will be sending this ticket to our level 3 department for further review. As soon as more details are available, we will be sure to notify you here.

————

once they are done with the analysis i will send you their results and login information

thanks

if i had installed it incorrectly, then it would not show up as a theme in WordPress. i have been running this site using Magazinly, and it worked fine with 2 other themes as well, so don’t think it is a problem with the server. the only theme that throws this error is Newsmag.

just to clarify, that by activating the theme i do not mean putting in my license code. i can’t get the theme to load and it throws a server error. i’ve tried deactivating all plugins and am running the most current version of wp