Search Results for 'css'

If that’s possible, I need to remove the product title from the breadcrumbs, not just hide it using CSS.
If there is no such possibility, then a CSS trick would be the last solution.

Looking forward to your feedback.

If that’s the case where should I add the css code? and what could be the css code used in it?

Hi Simon,

Thanks for getting back to me.

I’m extremely concerned and upset that this theme was allowed to release updates that included such a crippling and significant step backward in functionality. There are companies that have built entire lines of business around this product, and such big (negative) changes can have tragic results. We depend heavily on this, the most basic of theme functionality. To discover that it was overlooked is quite shocking. I’ve never encountered a theme that took away the ability to modify posts templates as part of an “update.”

I don’t want to go into specifics, but a large scale project that has been in development for months that was scheduled to launch this week was just completely derailed by this oversight. This is far more than an inconvenience.

We’ve already built multiple products around your theme, and so far we have loved it. But this significant change really bit us.

So the big question is what are our next steps?

We are not able to wait for future versions of the theme to address this oversight, as we need to release on time or risk significant losses.

We are not able to roll back to an older version of the theme, as that would set us back days and undo a lot of hard work, which we don’t have time for.

I don’t want to hack a custom solution that will prevent us from updating to future versions of the theme, since we need to keep it up to date for security reasons. So whatever we come up with ideally needs to be future-proof.

Here are our basic needs:

We need to be able to identify posts of a certain category, and then modify the post to do the following (based on Custom Fields values inside the post)

Enable/disable the following post elements:
Title, Date Display, Featured Image, Social Links, Related Posts. These can not just be toggled via CSS as we need to optimize load times.

We also need to inject unique custom html (which will contain meta data, CSS, javascript, tracking codes, pixels, etc) into each post for a specific category. This HTML is also sourced via Custom Fields values.

Without those abilities we can’t launch. This was something we could easily tackle in our other Newspaper theme installs.

I’m looking into using the “add_filter” method to process the posts to strip out HTML elements based on the Custom Fields values, but have yet to find a way to make this work. I’m also looking to do the same for injecting the HTML.

Further complicating things is the fact that we did not budget (from a time, resource, or financial perspective) adding additional development to this project, since we are basically re-instancing an existing product build.

I’m hoping you can help advise us here.

I do appreciate your feedback, and hope we can find a solution to this issue.

Thanks again!

I digested all that and found an easier way. I created a file editor-style.css in my child theme folder and put this in it.

html .mceContentBody-max-width-big {
background: none !important;
}

html .mceContentBody {
background: none !important;
}

That did the job and should survive upgrades too!

Hi everyone,

Not sure if this helps (and it’s certainly not the easy solution we’re all after), but here’s one way to delete those annoying empty columns that hang around in the TagDiv Composer.

Apologies in advance to all those out there who are far more advanced than me; I’m sure you probably already have this nailed and my explanation might not earn any marks for ‘technical writing’, but here goes…

The first thing to mention is that the words ‘Empty Column’ are slightly misleading, as a Column sits inside a Row – and so it’s usually the Row you want to target and not just the Empty Column inside of it. As clear as mud, eh?

Anyway, basically it’s a case of getting out of the TagDiv Composer, jumping into the old school Page Edit screen, and identifying in all that code where the empty rows / columns are and then deleting them from there.

So, if you’re using the TagDiv Composer and you put a new Row into your page, set it to stretch the the content, add a Text Column to it, put some text in (a sentence of Lorem ipsum in this case), hit save, it’ll look something like this when you look at the code on the Page Edit screen:

[vc_row full_width=”stretch_row_content td-stretch-content”][vc_column][vc_column_text] Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.[/vc_column_text][/vc_column][/vc_row]

And here’s the same thing but without the Text Column and actual text – the kind of thing that appears as an undeletable Empty Column in the TagDic Editor:

[vc_row full_width=”stretch_row_content td-stretch-content”][vc_column][/vc_column][/vc_row]

Apologies again to the hardcore users out there but I’m going to break that down in my own simple way so we all know what we’re looking at:

[vc_row full_width=”stretch_row_content td-stretch-content”] – (This opens the Row and stretches the content)
[vc_column] – (This opens the Column that sits inside the Row)
[vc_column_text] – (This opens the Text Column that sits inside the Column that sits inside the Row)
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. – (This is your text)
[/vc_column_text] – (This closes the Text Column that sits inside the Column that sits inside the Row)
[/vc_column] – (This closes the Column that sits inside the Row)
[/vc_row] – (This closes the Row)

And in the second example (the one without any Text or Text Column):

[vc_row full_width=”stretch_row_content td-stretch-content”] – (This opens the Row and stretches the content)
[vc_column] – (This opens the Column that sits inside the Row)
– (There’s nothing to see here, please move along…)
[/vc_column] – (This closes the Column that sits inside the Row)
[/vc_row] – (This closes the Row)

So, if you wanted to delete both of these so they no longer show up in the TagDiv Composer you’d have to delete all of the above.

At its most basic, if you spot [vc_row] [vc_column] [/vc_column] [/vc_row] in your code then that’s an empty Column / Row and (if you wish) you can delete it.

Needless to say, go careful with this. Because if you accidentally highlight a stray open or closed bracket and hit the delete button then you could be in all sorts of trouble. Probably best to add a Column that you know you don’t want and then have a go deleting that.

I’ve found that adding a text box and some text to an Empty Column actually makes it easier to distinguish in the code, so that’s not a bad idea.

Well, I hope that helps. As I said before, a big ‘Delete Empty Column’ button in the TagDiv Composer would be the best thing by far, it looks like it used to exist but I’ve only been using this theme for a couple of weeks so I guess I missed out – so until that comes back I’m sticking with this.

Even though it’s a total pain the arse.

Cheers,
Rich

PS: And if you feel in any way uncomfortable about doing this, then (as mentioned before by a few people) you can use the CSS tab on the Empty element to set the visibilty to ‘hidden’. It won’t remove it from the code but it will hide it from the Composer.

I’ve managed to do it via CSS, hovewer I’m not sure how good it will be in terms of responsivness and so.
Is there a better, simple and cleaner workaround than counting pixels ?

also please, how I can set up the shadow under the menu as almost every Newspaper menu have ? I want to put shadow only under the menu, not around it. Also only in the container, not full wide

Many thanks!!!