acmemediakits

Hi.
I guess the override function is triggered too early in your environment.
You may try to trigger the resize action later.

You can see the same setup running in this example:

Anyway, how to increase the function timeout?

1. open the file /wp-content/plugins/acme-divi-modules/public/js/acme-divi-modules-public.js

Starting at row 32 we have the following functions:

/**
     * ONLOAD Launcher
     */
    $(document).ready(function () {
        waitForFinalEvent(function () {
            if(false==isFrontBuilder())
                masonry_setup($('.acme_grid'));
            if($('.acme_carousel').length > 0) {
                var $et_pb_fullwidth_portfolio = $('.acme_carousel');
                $et_pb_fullwidth_portfolio.each(function () {
                    var set_container_height = $(this).hasClass('et_pb_fullwidth_portfolio_carousel') ? true : false;
                    set_fullwidth_portfolio_columns($(this), set_container_height);
                });
            }
        }, 40, 'callbackID');
    });

    /**
     * ON WINDOW RESIZE Launcher
     */
    $(window).resize(function () {
        waitForFinalEvent(function () {
            if(false==isFrontBuilder())
                masonry_setup($('.acme_grid'));
            if($('.acme_carousel').length > 0) {
                var $et_pb_fullwidth_portfolio = $('.acme_carousel');
                $et_pb_fullwidth_portfolio.each(function () {
                    var set_container_height = $(this).hasClass('et_pb_fullwidth_portfolio_carousel') ? true : false;
                    set_fullwidth_portfolio_columns($(this), set_container_height);
                });
            }
        }, 40, 'callbackID');
    });

At both row 46 and row 63 you will find this statement:
}, 40, 'callbackID');

The number 40 is currently the timeout value in milliseconds.
You can increase this value to an arbitrary time. I suggest you to try with 1000 and if the value is working for you, you can decrease that value to the minimum suitable.

As long as I can’t see your site, I can only guess.

Take care
mirko

Hi!
Those settings are driven by a JS that overrides Divi defaults.

You are supposed to fill the value for all the 5 resolution breakpoints.
In order to set only 1 column for all breakpoints you should fill this value:

View post on imgur.com

Here you can find a quick tutorial:
https://dev.acmemk.com/fw-portfolio-products/

• This reply was modified 8 years, 1 month ago by acmemediakits.

Please double check you filled the right informations, I have this trick working on a live environments:

Project Meta Field:

Preset setting:

As per your second question: yes it is possible to add it, but I think it is easier for you to set up a proper category so you can include only the projects you want to display.

• This reply was modified 8 years, 1 month ago by acmemediakits.

Hi! Glad to know it is clear ??

If you like my plugin, please share your love a give it some stars!

Anyway I will keep this thread open still for some days if you encounter any issue.

About the image size, I think I will add the feature you suggested in the next release: thank you for your hint.

Have a good job
Mirko

The query that calls the portfolio elements can work only for a post_type at once.

Anyway you can workaround this issue with the “override permalink” option.

How to manage this.

Let’s say you have 3 projects and 1 article you want to display in your portfolio:
The 3 project run under category “carousel”
The article url is: https://somesite.dom/my_featured_article/

Now we will add a new project with the category “carousel”: name it whatever you want, add a featured image and everything you want to be displayed in the carousel/portfolio.
Now scroll your page to “Custom Fields”, add a new custom field named, for instance, ‘slider_url’ and set it to: ‘https://somesite.dom/my_featured_article/’

Now go back to Acme Divi Modules settings, open your portfolio preset and fill the field “override permalink” with the value: ‘slider url’

You can use this workaround to link portfolio items from different post types.

For SEO purposes, add no-index/no-follow to the fake content page.

Hope this is clear, let me know if you need further assistance.
Take care
m

• This reply was modified 8 years, 1 month ago by acmemediakits.

Hi! Thank you for using my plugin.
As per the first question, let me investigate how can I implement this function and I’ll get back to you.

For the second issue, I don’t understand if you need to display both articles and custom post types in the same module/section or in the same page. Could you please clarify your question, please?

Take care
Mirko

Hi Diego.
I upgraded to PHP7 and I can confirm your plugin is working fine.
Take care

Thank you Diego for your answer.
Good to know php7 is supported

Take care
mirko

Hi Bob, just released a fix to this issue.
I limited jquery-ui only to my settings page.

Thank you for helping me improve my plugin.

Hi bob.
are you experiencing this issue on a live installation? May you provide me link/access?

This randomly happens. The js of my plugin are triggered after 40ms of page load. Sometimes they trigger before main divi js. In this case just refresh the page and the page should be visible.

If you are confident with javascript you can try to edit the file
./acme-divi-modules/public/js/acme-divi-modules-public.js

at row 46 changing from:

}, 40, 'callbackID');
to
},400, 'callbackID');

this will delay the $(document).ready event.

Hi Manas.
That value, with the module enabled and with no preset, is correct.
The issue is with the settings page, not with the plugin itself.

Could you please provide me the following file:
/wp-content/plugins/acme-divi-modules/admin/partials/acme-divi-modules-admin-display-abmp-post_type-loop.php

Thanks

Hi Manas,
could you please try to delete the plugin options?

You can do this by accessing your db via phpMyAdmin, then

open table: wp_options
search for option_name = acme-divi-modules-abmp
then clear its option_value

once you did this operation, go back to the module settings page and activate the extended portfolio once again.

Thanks
Mirko

• This reply was modified 8 years, 2 months ago by acmemediakits.

Hello, I’m afraid you had this issue. I can’t replicate the error on my development area.
On my siteground environment I have full compability WP 4.7 Divi 3.0.25 and plugin 1.2.4
I don’t have the chance to test it on a WAMP server, so I cannot assure you it is working on your environment.

So, I can only guess the problem and suggest these solutions (in this order):
1. remove the plugin and install it back again (the line number for the parse error actually doesn’t match the current endif; statement)
2. check if your presets refer to a missing post_type
3. check some third party plugin conflict.

Thank you for downloading. If you like my plugin, please drop some star!
Take care