[bluecouches]

This reply has been marked as private.

[bluecouches]

Swift Framework: 2.4.15
Atelier: 2.3
Wordpress: 4.6

The old line was already commented out when I checked the file, but still no attribute search. Also just set up another test attribute gave it some terms, and added them to a published product, but no luck.

else {
                        //$sf_ss_dropdown .= '<a class="ss-option" href="#" data-attr_value="' . $term->term_id . '">' . $term->name . '</a>';
                        $sf_ss_dropdown .= '<a class="ss-option" href="#" data-attr_value="' . $term->slug . '">' . $term->name . '</a>';
                    }

[bluecouches]

Well thanks for looking into it.
I still can’t get it to repeat on 2016, but I’ll leave it alone for now.

Just out of curiosity, where were you able to find this issue in Yoasts support? I could’t find anything in the past couple months on GutHub related to this issue.

Thanks for the help!

[bluecouches]

Can you provide a filter we can use in functions.php to avoid having to change this after each update?

Any help is much appreciated! Thanks!

[bluecouches]

Hi Mohammad,

This change was already present in my sf-supersearch.php file.

$sf_ss_dropdown .= ‘slug . ‘”>’ . $term->name . ‘‘;

However, Super Search is still not searching product attributes. I have some fairly unique strings like “HF21A” set as product attribute terms. I get 0 search results when using super search to look for this string.

I thought that I might have to have the attributes set to “show on product page” in the product data meta, but even with that setting enabled, there are no results.

Any help would be greatly appreciated. I can start a new topic if need be.

Thanks
Mohammad

[bluecouches]

I’m sorry, I’m not sure which directory plugin you’re referring to. I have the default custom post type, Directory, which is included with the theme. But I have no separate “Directory” plugins installed.

The type error / conflict only occurs when enqueueing jQuery datatables js.

[bluecouches]

That’s It! Thank you very much David. This is exactly what I was searching for… works perfectly.

[bluecouches]

This reply has been marked as private.

[bluecouches]

Please read my reply. I have already done that and explained that it has no effect on the “Recent Posts” page builder element.

I was very thorough in testing both options given to me, I explained that they appear to ONLY change the BLOG page thumbnails and have no effect on the “Recent Posts” page builder asset that I want to use on a completely separate page.

[bluecouches]

The CSS suggestion had no effect unfortunately. .thumb-media-image references the blog page thumbnails and not the thumbs used in the “Recent Posts” SPB Element.

I’ve also added the code you linked to functions.php and the result changed the thumbnails shown on my blog page depending on the image sizes I changed… But this too has no effect on the “Recent Posts SPB Element.”

I fear your advice may be for changing thumbnails on the blog page only and not the actual Swift Page builder element. For reference, I’ll be including a “Recent Posts” SPB element on a new page and would like the thumbs to be displayed at 3×4 as opposed to the standard 4×3.

There is a similar question here for the Atelier theme that was solved via email by Kyle: http://www.swiftideas.com/forums/topic/question-re-recent-posts-standard-row-thumbs/

[bluecouches]

I have temporarily fixed. Please disregard.

The problem occurred on all pages with a portfolio page builder element after editing categories and assigning new categories to various portfolio posts.

Manually updating each page builder portfolio element to include the new categories seems to have fixed the problem.

The problem only affected page builder elements in which the “all” category had been set.

[bluecouches]

We are experiencing the same issues. Is there a solution to this?

[bluecouches]

Thank you, I appreciate that. The coordinates were in there before the update, and all of the maps worked fine. Updating the theme must have lost them somehow.

Also, when you updated those pages, I lost some of my responsive classes that I had entered in certain elements of the page. They are all visible now. It seems like every time I update a page I lose those added classes e.g. “hidden-sm”.

I’m going to re-layout the page to fix that using built in responsive features of the page builder. I used classes instead of the built in function for responsive visibility because I can use 4 sizes: hidden-xs, hidden-sm, hidden-md, hidden-lg versus the built in responsive visibility with only 3: phone, tablet, desktop.

[bluecouches]

The problem occurs on these 3 pages:

Lynn Plaza

Roygate

http://nwapt.com/buildings/bel-15/

[bluecouches]

Since no one ever replied to this. Can someone from support chime in with an answer?