Hi Ismael,

Thanks for the clear explanation about the sorting script.
I do understand the why, i.e. giving the user freedom to select any combination of cats/subcats, but it just feels counterintuitive to me to have to exclude the parent when using subcategories :-)
It’s just something I need to add to my “that’s just the way it is” list.

Kind regards,
Rob

Hi Mike,

Sure the issue is there, I know that and you just confirmed what I already knew.
That’s why I was asking for insight into the difference between the two cart deletion methods. Like you can read above.

What I do definitely NOT appreciate is you disabling the password mode on this staging site. Why oh why would you touch that?
That is there to PREVENT access to the general public to the staging – still allowing external support like yours through the Temporary Login link for admins (DIFFERENT plugin!). This is a staging site, it is NOT supposed to be accessible from the outside (as there is also a LIVE site somewhere), and you messed that up by leaving the cached version active AFTER disabling the password protection. There was absolutely NO reason whatsoever for you to do that, because, as I explained above, the settings were already available for testing through pages being cached also for logged in users aka admins aka Enfold support. You just needed to hit “visit site” from the Dashboard.

I fixed it now, but this sort of thing does not really enforce my trust in Enfold support per se.
I know you guys have a lot on your plate, but properly reading and thinking about what you do on a site (even if staging) should be part of the package…

Kind regards,
Rob

• This reply was modified 5 years, 8 months ago by rob2701. Reason: added note about Temporary Login and Password Protect being 2 different plugins

Hi Rikard,

Any text-widget really. Check the home page footer text-widgets (col 1,2 and 3).
Link to staging in private. See bottom of QuickCSS.

Kind regards,
Rob

NOTE:
I also changed the rule to #id li (since the list-style property applies to list-items li, not the container ul).
But that doesn’t work either.
I think this may be because Enfold has decided to set list-style-type to NONE in the base css and then adds classes to achieve circle, disc, square etc.
The other way around would maybe have been handier, i.e. add a class for .no-bullet or something instead of changing the default behavior?
Anyways, I stil want to get this to work the normal way, and not even targeting the specific page will work in the current setup. :-)

• This reply was modified 5 years, 8 months ago by rob2701.

Hi,

Thanks for taking the time to look at this. Unfortunately though, the test page you set up proves my point about the illogical nature of the choices exactly :-)

As you can see:

• 1. instead of just choosing the parent to get sorting, you need to choose ALL subcategories to display sorting
• 2. IF, like you did, you ALSO choose the parent category, then you get a DUPLICATE, i.e. PARENT = also ALL. In other words, ALL and PARENT are identical.
• 3. Conclusion: the PARENT needs to be excluded to get a proper sorting in the portfolio grid. This is not logical i.m.o. and this was exactly my point.

Perhaps one of the devs can explain the why and how of this arrangement?

Kind regards,
Rob

P.S.:
Trying to warn here also about some possible illogical behaviour with this “free to choose a combination of all subcategories from various parents”.
For exampke consider this scenario:
if you have 2 different portfolio cats, each with subcats, and both have a subcat with the exact same name, say “sour fruits”, then what would be the result in the sorting options? Would they display separately in the sorting or be merged even if belonging to different parents? Just saying.

• This reply was modified 5 years, 8 months ago by rob2701. Reason: added explanation of why I'm worried about this

Sure, close when you want. It was solved anyway :-)

Kind regards,
Rob

• This reply was modified 5 years, 8 months ago by rob2701.

Hi Rikard,
Sure, details in the private message block.
See the Privacy Policy page (which has multiple headers following each other).
Then uncomment the CSS code for h1+h2, etc. in the Quick CSS.
Then visit the page again.

Regards,
Rob

hI,
For anyone interested in follwoing the same route as me to serve up double-size retina images with high compression to all devices, here’s what I did.

functions.php in child theme:

// remove "responsive images" functionality in WP 4.4 and higher
add_filter('wp_get_attachment_image_attributes', function($attr) {
   if (isset($attr['sizes'])) unset($attr['sizes']);
   if (isset($attr['srcset'])) unset($attr['srcset']);
   return $attr;
}, PHP_INT_MAX);
add_filter('wp_calculate_image_sizes', '__return_false', PHP_INT_MAX);
add_filter('wp_calculate_image_srcset', '__return_false', PHP_INT_MAX);
remove_filter('the_content', 'wp_make_content_images_responsive');

// Disable loads of Enfold & WP image sizes upon upload
// do image sizes manually, double-size with high compression for retina screens
// use Photoshop to set exact double size and quality between Q30 and Q40
add_action('init', 'remove_enfold_image_sizes');
function remove_enfold_image_sizes() {
// do NOT remove widget size, is used in backend portfolio items!
// remove_image_size('widget');
	remove_image_size('square');
	remove_image_size('featured');
	remove_image_size('featured_large');
	remove_image_size('portfolio');
	remove_image_size('portfolio_small');
	remove_image_size('gallery');
	remove_image_size('magazine');
	remove_image_size('masonry');
	remove_image_size('entry_without_sidebar');
	remove_image_size('entry_with_sidebar');
	remove_image_size('shop_thumbnail');
	remove_image_size('shop_catalog');
	remove_image_size('shop_single'); 
  remove_image_size('shop_gallery_thumbnail');
}
// Remove unneeded WP image sizes
add_filter( 'intermediate_image_sizes_advanced', 'prefix_remove_default_images' );
// Remove default image sizes here. 
function prefix_remove_default_images( $sizes ) {
// do NOT remove small and medium sizes, they are used in backend Media Library!
// unset( $sizes['small']); // 150px
// unset( $sizes['medium']); // 300px
 unset( $sizes['large']); // 1024px
 unset( $sizes['medium_large']); // 768px
 return $sizes;
}

List of Enfold/TopMenu image sizes for different image ratios:

w = standard width Enfold
Rw = doubled Enfold width for Retina
GR = Golden Ratio

ENFOLD WITH Top menu

full width header banner frontpage
w 1519 x 430 / Rw 3040 x 860
>>>>> USE:
4:1 > 3000 x  849

news featured
w 81 x 81 / Rw 162 x 162
>>>>> USE:
1:1 > 180 x 180
1:1 > 360 x 360

portfolio 2 column featured
w 758 / Rw 1516
>>>>> USE:
4:3  > 1600 x 1200
3:2  > 1600 x 1067
16:9 > 1600 x  900
GR   > 1600 x  991

portfolio 3 column featured
w 507 / Rw 1014
>>>>> USE:
4:3  > 1024 x  768
3:2  > 1024 x  683
16:9 > 1024 x  576
GR   > 1024 x  624

portfolio 4 column featured
w 378 / Rw 756
>>>>> USE:
4:3  >  800 x  600
3:2  >  800 x  533
16:9 >  800 x  450
GR   >  800 x  496

portfolio single full width
w 1419 / Rw 2838
>>>>> USE:
4:3  > 3000 x 2250
3:2  > 3000 x 2000
16:9 > 3000 x 1688
GR   > 3000 x 1858

portfolio single 2/3
w 918 / Rw 1836
>>>>> USE:
4:3  > 1920 x 1440
3:2  > 1920 x 1280
16:9 > 1920 x 1080
GR   > 1920 x 1189

portfolio single 3/4
w 1043 / Rw 2086
>>>>> USE:
4:3  > 2500 x 1875
3:2  > 2500 x 1667
16:9 > 2500 x 1406
GR   > 1920 x 1549

gallery with right sidebar
w 986 / Rw 1972
>>>>> USE:
4:3  > 2000 x 1500
3:2  > 2000 x 1333
16:9 > 2000 x 1125
GR   > 2000 x 1239

store multi product
w 320 / Rw 640
>>>>> USE:
4:3  >  640 x  480
3:2  >  640 x  427
16:9 >  640 x  360
GR   >  640 x  396

store single product 1/2
w 667 / Rw 1334
>>>>> USE:
4:3  > 1440 x 1080
3:2  > 1440 x  960
16:9 > 1440 x  810
GR   > 1440 x  892

5 column featured
w 216 / Rw 432
>>>>> USE:
4:3  >  480 x  360
3:2  >  480 x  320
16:9 >  480 x  270
GR   >  480 x  297

3/5 of page
w 817 / Rw 1634
>>>>> USE:
4:3  > 1800 x 1350
3:2  > 1800 x 1200
16:9 > 1800 x 1013
GR   > 1800 x 1115

Hi,

Spoke too soon about closing the ticket… :)
Creating subcategories in one portfolio parent category I discovered some behaviour which I cannot seem to solve.

Code above works fine as long as there are no subcategories, highlights menu parent perfectly.
However, when I add 3 subcategories under MenuItem/PortfolioCat A (A1,A2,A3) in order to have sorting, the behaviour becomes unpredictable:

• in the portfolio grid I cannot just choose the parent Category-A, I have to choose to display A+A1+A2+A3, otherwise I get no sorting. Shouldn’t subcategories be included by default?
• however, now I get in the sorting all/subcatA1/subcatA2/subcatA3/catA… what is catA (the parent doing there? There is already ALL…
• If I only choose catA itself for the portfolio grid display, then of course I have proper menu highlighting but no sorting…

I appreciate any help or insight you can give me.

Thanks in advance,
Rob

Hi Vinay,

Yes, like you can read above I figured out everything EXCEPT the portfolio items.
Can you please read above before responding? :-)
As you can see from the site, opening a PORTFOLIO item highlights ALL 3 portfolio menu items, even though the CSS says the colours are restricted to 1 portfolio menu item only…

Regards,
Rob

So to make it more clear:

Go to menu item “Golden Ratio” (menu item is set to highlight purple)
Open a portfolio item in there
See all 3 portfolio menu items highlighted (blue-orange-purple)
So the other 2 portfolios get highlighted as well, even though they are different portfolio categories on different pages with different menu items and different colors specified.

• This reply was modified 5 years, 8 months ago by rob2701. Reason: Added explanation for clarity

Hi,

I added this CSS below to clarify the problem.

There are 3 different portfolios (= categories/taxonomies).
– Each portfolio has a separate menu item (top level, not nested)
– Each portfolio grid on each page is restricted to display 1 portfolio category
– ALL portfolio items have been assigned a proper category
– ALL portfolio items have proper parent set for breadcrumbs

Problem:
Even though the CSS “should” be restricted to each separate menu item ID, still on opening a portfolio item ALL portfolio cats/taxonomies/menu-entries get highlighted…

When you can, please help me understand this behaviour, because I’m lost now.

/* -------------------------------------------------------------- */
/* TEST PORTFOLIO ITEM CAT PARENT HIGHLIGHT BELOW */
/* TEMP DIFFFENT COLOURS TO SEE THE DIFFERENCES */

/* Portfolio A - Menu ID = 765 */
/* hover over "Remove" button of menu item to see ID */
/* HIGHLIGHTS ALL PORTFOLIO CATS even while restricted to only this menu item */
/* highlight Portfolio menu item when portfolio item open */

body.single-portfolio .main_menu ul li#menu-item-765 a .avia-menu-text  {
/*  color: #719430 !important; */
  color: blue;
}
/* highlight bottom border when menu top header */
body.single-portfolio .main_menu ul li#menu-item-765 a {
/*  border-bottom: 2px solid #719430 !important; */
  border-bottom: 2px solid blue;
}

/* Portfolio B - menu ID = 764 */
/* hover over "Remove" button of menu item to see ID */
/* HIGHLIGHTS ALL PORTFOLIO CATS even while restricted to only this menu item */
/* highlight Portfolio menu item when portfolio item open */
body.single-portfolio .main_menu ul li#menu-item-764 a .avia-menu-text {  
/* color: #719430 !important;  */
  color: orange!important;
}
/* highlight bottom border when menu top header */
body.single-portfolio .main_menu ul li#menu-item-764 a {
/*  border-bottom: 2px solid #719430 !important; */
  border-bottom: 2px solid orange;
}

/* Portfolio C - menu ID = 1038 */
/* hover over "Remove" button of menu item to see ID */
/* HIGHLIGHTS ALL PORTFOLIO CATS even while restricted to only this menu item */
/* highlight Portfolio menu item when portfolio item open */
body.single-portfolio .main_menu ul li#menu-item-1038 a .avia-menu-text  {
/*  color: #719430 !important; */
  color: purple;
}
/* highlight bottom border when menu top header */
body.single-portfolio .main_menu ul li#menu-item-1038 a {
/*  border-bottom: 2px solid #719430 !important; */
  border-bottom: 2px solid purple;
}

• This reply was modified 5 years, 8 months ago by rob2701. Reason: corrected some typos

Hi Yigit,
I have the reverse proxy setup to the local devsite running, so it’s now accessible with password from the outside.
Let me know when you have time and are a little less busy, then I can create a temporary login without password link for you.
No hurry though (it’s just a dev site for now)
Rob

• This reply was modified 5 years, 9 months ago by rob2701.

Hi Yigit,

Unfortunately not yet possible, still working on a local development server and have not yet set up the reverse proxy.

Rob

After some more testing, thinking and testing:

1.
Changes to the thumbs array in the child theme DO work. I must have done something wrong last time. Sorry.

2.
After a bit of thought I’ve decided that its much more efficient for me to do the exact double-size high compression images by hand and then upload.
While it’s nice to have the theme automatically do resizing and cropping, it just results in much heavier images, most of which I will not use anyway..

3.
I have commented out all thumbnails sizes in the child theme functions.php therefore..
Thus regenerating thumbs loses all other sizes (except the WP ones for the Media Library).
Going to try just using the full size original and having the theme CSS do downscaling.

You can mark this topic as solved. I hope. Unless I’ve made a wrong assumption somwhere down the line :-)

Hi Enfold Team, I tested this out in hte meantime but am baffled by the results :-)
Can you help me understand?

I doubled the thumb sizes in the child theme functions.php:

// – set WordPress compression of image and thumbnails on upload and resize to 90 or higher
// images are manually resized, compressed and optimized BEFORE upload already
// WP compression on images on resize/for thumbnails is standard = 82
add_filter(‘jpeg_quality’, function($arg){return 90;});

// remove “responsive images” srcset functionality in WP 4.4 and on from this theme
remove_filter( ‘the_content’, ‘wp_make_content_images_responsive’ );

// double-size thumbs for Retina screens and zoom
$avia_config[‘imgSize’][‘widget’] = array(‘width’=>72, ‘height’=>72); // small preview pics eg sidebar news – ORG 36 x 36
$avia_config[‘imgSize’][‘square’] = array(‘width’=>360, ‘height’=>360); // small image for blogs – ORG 180 x 180
$avia_config[‘imgSize’][‘featured’] = array(‘width’=>3000, ‘height’=>860); // images for fullsize pages and fullsize slider – ORG 1500 x 430
$avia_config[‘imgSize’][‘featured_large’] = array(‘width’=>3000, ‘height’=>1260); // images for fullsize pages and fullsize slider – ORG 1500 x 630
$avia_config[‘imgSize’][‘extra_large’] = array(‘width’=>3000, ‘height’=>3000, ‘crop’ => false); // images for fullscrren slider – ORG 1500 x 1500
$avia_config[‘imgSize’][‘portfolio’] = array(‘width’=>990, ‘height’=>800); // images for portfolio entries (2,3 column) – ORG 495 x 400
$avia_config[‘imgSize’][‘portfolio_small’] = array(‘width’=>520, ‘height’=>370); // images for portfolio 4 columns – ORG 260 x 185
$avia_config[‘imgSize’][‘gallery’] = array(‘width’=>1690, ‘height’=>1368); // images for portfolio entries (2,3 column) – ORG 845 x 684
$avia_config[‘imgSize’][‘magazine’] = array(‘width’=>1420, ‘height’=>750); // images for magazines – ORG 710 x 375
$avia_config[‘imgSize’][‘masonry’] = array(‘width’=>1410, ‘height’=>1410, ‘crop’ => false); // images for fullscreen masonry – ORG 705 x 705
$avia_config[‘imgSize’][‘entry_with_sidebar’] = array(‘width’=>1690, ‘height’=>642); // big images for blog and page entries – ORG 845 x 321
$avia_config[‘imgSize’][‘entry_without_sidebar’]= array(‘width’=>2420, ‘height’=>846); // images for fullsize pages and fullsize slider – ORG 1210 x 423
$avia_config[‘imgSize’] = apply_filters(‘avf_modify_thumb_size’, $avia_config[‘imgSize’]);

Save and regenerate thumbs.
But then I watch the regenerated thumbnails and they seems to be back to the standard sizes.
These are the currently registered thumbnail sizes, whether they exist for this attachment, and their filenames:

thumbnail: 80×80 pixels (cropped to fit)
medium: 300×300 pixels (proportionally resized to fit inside dimensions)
medium_large: 768×0 pixels (proportionally resized to fit inside dimensions)
large: 1030×1030 pixels (proportionally resized to fit inside dimensions)
widget: 36×36 pixels (cropped to fit)
square: 180×180 pixels (cropped to fit)
featured: 1500×430 pixels (cropped to fit)
featured_large: 1500×630 pixels (cropped to fit)
extra_large: 1500×1500 pixels (proportionally resized to fit inside dimensions)
portfolio: 495×400 pixels (cropped to fit)
portfolio_small: 260×185 pixels (cropped to fit)
gallery: 845×684 pixels (cropped to fit)
magazine: 710×375 pixels (cropped to fit)
masonry: 705×705 pixels (proportionally resized to fit inside dimensions)
entry_with_sidebar: 845×321 pixels (cropped to fit)
entry_without_sidebar: 1210×423 pixels (cropped to fit)
shop_thumbnail: 100×100 pixels (cropped to fit)
shop_catalog: 300×300 pixels (cropped to fit)
shop_single: 600×0 pixels (proportionally resized to fit inside dimensions)
woocommerce_thumbnail: 300×300 pixels (cropped to fit)
woocommerce_single: 600×0 pixels (proportionally resized to fit inside dimensions)
woocommerce_gallery_thumbnail: 100×100 pixels (cropped to fit)

Thanks in advance for your help (I see you’re a bit flooded with help requests now…)

• This reply was modified 5 years, 9 months ago by rob2701.