The bug is in themes/salient/nectar/tinymce/shortcode-processing.php line 1529:

if($masonry_layout 'false' || $layout ‘3’ || $layout == ‘4’)

This if has line 1540 which changes $regular_size:

$regular_size = wp_get_attachment_image_src($featured_ID, ‘portfolio-thumb’, array(‘title’ => ’’));

If this is intentional and masonry is not supposed to work with 3 or 4 column layouts then don’t offer the damn option. And if it’s intentional… WHY!!! Why would you not offer a masonry layout in 3 or 4 columns?

All you need to do is wrap line 1540 in an if block:

if ($masonry_layout == ‘false’) { $regular_size = wp_get_attachment_image_src($featured_ID, ‘portfolio-thumb’, array(‘title’ => ’’)); }

Fix this ridiculous convoluted mess of a theme.

Hey Brian987511,

The masonry option requires a fullwidth compatible layout to be enabled. The “fullwidth constrained” layout option was added a little while ago to allow the possibility of a non fullwidth masonry layout as seen in this demo. As stated in the layout description, “The Constrained Fullwidth option will allow your projects to display with the same formatting options only available to full width layout” – you can use that as a starting point and further CSS could be added if you dislike the column sizing. If you’d like assistance tweaking that, please share your URL in regards.

Do you honestly think I didn’t try Constrained Fullwidth out of the whopping 4 options available? 1. Constrained Fullwidth does not work with a Full Width Content row (god knows why). 2. Constrained Fullwidth only shows 2 columns on a large monitor. I don’t have the time to try and reverse engineer this garbage code anymore to figure out how I can get the simple layout I need with Constrained Fullwidth (and I’m sure it would require me patching the theme myself yet again). It’s honestly pathetic that this theme can’t accomplish such simple tasks (1/4 + 3/4 full width row with a masonry 3 column portfolio in the 3/4 column).

So I’ll ask again. Why do you offer the option for a masonry layout with 3 columns if it isn’t supposed to work? And why do you exclude the masonry layout with 3 columns? All you need is one if block in that code!!!

Hey tradeart, could you kindly elaborate a little further on what you’re referring to – are you referring to being able to adjust the version number from your end?

Cheers

Sorry – I should have been more clear.

I did eventually find the current version, at the very bottom of the very, very long “Item Details” tab. It’s just that it’s not a useful place for the version. Counter intuitive as well. There is all this great, useful information on the right panel, like compatibilities, wordpress versions, etc., and it would be nice if Version was listed there. Something like this (mockup) https://www.screencast.com/t/kov3xsuHk6

I realized of course this probably isn’t up to you as an author. I don’t know. I was just suggesting it would be nice to have that available easily. For the 85,000+ of us who purchased this, (and I have 10 licenses of it) we need to reference this “current version” data regularly. So, to have to search and search to find the current version… When it should be in the table on the right… seems like bad UX.

I’m not complaining TO you at all. I’m a huge fan of Salient. I’m so impressed you’ve come so far. I recommend Salient as often as I can. But maybe as a big author you have some pull with Envato and can suggest it.

Cheers

But, can I ask? Why you removed attributes/categories slug in portfolio section? What is the point of this action? Now all my portfolio attributes work only with that link structure – “{anything what I choose for BLOG in permalincs section, I choosed “blog” so} – blog/project-attributes/{name}” and it can’t changed, because there is no such option in portfolio functionality, also in wp permalinks there is no such option. It must be separated as before.

Also, in portfolio section Masonry Grid Sizing you can found “Sqaure” instead of “Square”

Hey RIVEMOTION, glad to hear you’re still enjoying it

1. We haven’t changed anything with the permalink structuring of the project-type or project-attributes taxonomies, however a workaround that would help with your custom base would be to edit this:

'rewrite' => array( 'slug' => 'project-type' )

to be this

'rewrite' => array( 'slug' => 'project-type', 'with_front' => false )

in the functions.php file – after you make the change, resave your permalink structure in Settings > Permalinks

2. Thanks for letting me know

Cheers

Hello, thanks. Tried, it’s working only with categories, not with attributes. I mean, why portfolio categories and attributes goes with standart permalink structure? It was created for pages and blog, no? Anything I add in there, affects portfolio categories/attributes. In the same time, I can “choose” custom slug only for portfolio page, why attributes/categories don’t see it and don’t show up there instead of blog page? My blog meta show up with same link by the way… I remember that I could choose it for attributes and categories also, don’t remember where exactly, but I remember that I could without editing files. It was like “website.com/blog”, “website.com/projects”, “website.com/projects/atts/unique”, “website.com/projects/cats/unique” and there was no problem, now I can’t do it from admin area.

Right now my blog categories looks like – “website.com/blog/cats/somename”, I want same for portfolio, make it look like – “portfolio/cats/somecatname”, and “portfolio/atts/someattname”. Just don’t understand why I have that option to add custom slug if categories and attributes don’t work with it.

Okay, I’ve changed two lines, it’s working, but I really don’t like the way I did it, you update Salient oftenly, everytime I must change it to make it work right? Well, it could be easy and awesome, if that information could be stored in database, not in functions.php which must be edited everytime…I hope you add such an easy slug options in next update, it would be just awesome, because I can change portfolio slug, but can’t change att/cat slugs. Thanks.

Hey RIVEMOTION, you can actually copy the entire nectar_add_portfolio_taxonomies function into a child theme and make the modification there

Hello. Wow, really? I didn’t know until now why I need that child theme, yesterday I saw child theme on different template with almost no files…now it have sense. Thank you, will try…Anyway, I think such an option must be in dashboard, why making everything more difficult?

Not sure what I did wrong with child theme….just activated and boom.

Few similar errors -

Warning: session_id(): Cannot change session id when headers already sent in plugins\premium-seo-pack\aa-framework\framework.class.php on line 563

Warning: session_start(): Cannot start session when headers already sent in \plugins\premium-seo-pack\aa-framework\framework.class.php on line 566

Warning: Cannot modify header information – headers already sent by (output started at \wp-content\themes\salient-child\functions.php:86) in \wp-admin\includes\misc.php on line 1126

Tried disabling plugin, only last error remains with misc.php

Contacted them already, but maybe you know what is wrong? Since it’s your child theme)))

Also page transition with double solid just broke and begins the transition before it completely closes the page

Don’t know what’s happening…updated few times options and settings while all plugins was disabled and all is gone somehow even with plugins enabled. Probably browser or configs problem.

Hey RIVEMOTION, there’s currently no known issue with the child theme that could cause errors like that - please either open a ticket in regards with a temporary admin login via the support forum, or reach out in regards via the contact form on my author page with the same: https://themeforest.net/user/themenectar

Hello Nectar! All is ok. But now I have some strange problems, when I activate Salient template, I see NO “Install Plugins” suggestions, also no such menu in appearance, with other templates all is ok. Did I broke something? I reinstalled few times the template…ANd how to fix it? I tried, even load is longer now…How to clean database from any mistake/error? Working on local, so I can’t show you, just asking.

And also when choosing Child Theme, custom styles for redux framework not working.

Hey RIVEMOTION,

It would be hard to figure out exactly what’s going on with the setup without being able to take a look since I haven’t seen issues like that before – does the the “Appearance > menus” item display again when you disable Salient?

What you mean by “menus”? Only “install Plugins” Or “Required template plugins”, that exactly thing – is not working, when I try to activate other template all is ok, but not with salient, it’s just gone, so I can’t for example activate visual composer, contact form 7 etc, so I activated manually…Tried to reinstall template, no results, something in database I think, after import same thing happening. Can I for example paste everything on host and somehow send a link to you?

Don’t know what is wrong, but have no time for this, just reinstalled everything and preparing for imports.

Also http://joxi.ru/a2X3jZnSw403Vm.png on 4k resolution and with width 2000px (that is set in salient options, it think it’s 2000px) my thumbnails don’t touch right corners of block in portfolio.

I found a bug. If I have portfolio in ”/portfolio/” and try to add a child page to “portfolio” page as parent page to make it look like ”/portfolio/somepage/” i get 404, when I change portfolio slug to something else it’s working, but I need exactly portfolio or project or whatever it can be, but portfolio page + child page, and it’s not working, tried without plugins, even clean wp and theme install, updated permalinks like 100 times, no luck. I remember in old salient it worked, I had portfolio and few pages above it as child pages.

Hey RIVEMOTION,

1. Are you using a featured image or custom thumbnail upload for your project image(s)? Could you also let me know the portfolio element layout setting you’re using so I can replicate it on my end?

2. The portfolio post type slug behavior has not changed in recent releases, the issue you’re describing has always been there since it’s how WordPress handles custom post type slugs by default. i.e. slugs after the post type are seen as single posts (projects) rather than pages, so when you hit the URL /portfolio/somepage, it’s looking for a project named “somepage” not a page. Did you perhaps in your old setup have a different permalink structure to allow that – as it would require a workaround natively https://wordpress.stackexchange.com/questions/163104/404-on-child-page-when-parent-page-slug-is-identical-to-custom-post-type/166211

Thanks in advance

Hey SiamNinja,

if you’ve already tried to clear your browser cache, kindly share your URL in regards so I can take a look

Thanks in advance

Thanks fo reply. Yes, I clear all cache incl. from Cloudflare side.

Here is blog website link: https://airlean.com/blog/

ONLY on mobile device no more overlay on blog image preview widget and in every single blog post – no overlay on header image.

Hey SiamNinja,

Add this into the custom css box located in the Salient options panel > general settings > css/script related tab

body[data-remove-m-parallax="1"].using-mobile-browser #page-header-bg[data-parallax="1"] .page-header-bg-image {
  opacity: 0.3;
} 

Cheers

Thanks a lot!

But one problem still remain: - on main blog page if I want to add full screen header blog-slider – background image (featured image) not visible anymore, just dark blank background.

Also only on mobile after update. Something is changed and blocking of displaying background cover blog image.