Marj Wyatt

Thanks, @jcastaneda

I guess I’m more comfortable with the 5-minute install procedure that I learned many years ago. It is documented here:
https://developer.www.ads-software.com/advanced-administration/before-install/howto-install/

Maybe I’ll just write all this off as an anomalous mystery that will never be solved. But, because I am no curious, I may try a manual install at another unused Cpanel on my VPS account and see if the problem recurs.

@jcastaneda

What is a Composer build?

My VPS is through A2. I outlined the steps I took for the installation. Those are the steps I’ve always taken.

@jcastaneda

I don’t think it is a hosting level thing. I have a VPS that is completely within my own control.

I wondered if the manual installation process had changed or if there was some data leftover from the development process.

• This reply was modified 1 year, 7 months ago by Marj Wyatt.

Thank you for your reply, @t-p

Resaving permalinks does eliminate the 404s. The problem is the frequency with which we have had to do this. That’s why I created this inquiry on the forum.

When I mentioned I had done the check for rogue plugins, it was a manual plugin check procedure wherein I disabled all non-essential plugins (Wishlist Member is essential) and re-enabled them one-by-one. No errors manifested.

This morning, the site is not returning 404 errors when top-level categories are tapped from the menu so permalinks did not need to be resaved. But the development site in the sandbox is. I’ll do a little more digging over there.

Your second example is the situation at the development. Each video is unique. Here’s an example from one post.

CODE100

<center><div id="evp-5e50e94bc9e2d78d5a1e7991d60d5019-wrap" class="evp-video-wrap"></div><script type="text/javascript" src="https://www.vegetablefruitcarving.com/easy_vid_play/framework.php?div_id=evp-5e50e94bc9e2d78d5a1e7991d60d5019&id=MS1wZWVsYW5kcm9zZXN1cmxub3RkZWludGVybGFjZWQtMW00di0xLm00dg%3D%3D&v=1340321922&profile=default"></script><script type="text/javascript"><!--
_evpInit('MS1wZWVsYW5kcm9zZXN1cmxub3RkZWludGVybGFjZWQtMW00di0xLm00dg==[evp-5e50e94bc9e2d78d5a1e7991d60d5019]');//--></script></center>

CODE101

<center><div id="evp-69456d05828b611f8c698b1785cbb086-wrap" class="evp-video-wrap"></div><script type="text/javascript" src="https://www.vegetablefruitcarving.com/easy_vid_play/framework.php?div_id=evp-69456d05828b611f8c698b1785cbb086&id=Mi1jYWtlLWFuZC1taXN0YWtlcy11cmwtZGVpbnRlci0xbTR2LTEubTR2&v=1340322210&profile=default"></script><script type="text/javascript"><!--
_evpInit('Mi1jYWtlLWFuZC1taXN0YWtlcy11cmwtZGVpbnRlci0xbTR2LTEubTR2[evp-69456d05828b611f8c698b1785cbb086]');//--></script></center>

I’ll proceed on the path, assigning each video in every post a different CODExxx. You’ve been very responsive to my inquiries, so I’m sure you’ll come up with a fix quickly if I hit some unforeseen maximum.

Thanks, David.

Well, if you’re telling me that I can reuse CODE100 on multiple posts, that doesn’t gel with what I had experienced. When I read over the documentation, it seemed to suggest that I could not reuse the same CF name.

My scenario is that there is different embed code for each custom field, each embed code calling different videos. I assumed, when I read the documentation, that I could reuse the code for your plugin if it referred to the same content in the custom field.

When using EmbedIT, we could name custom fields for each post, beginning with HTML1.

What am I misinterpreting?

Anyway, I am soldiering on and using a different CODExx for each custom field where I’m replacing EmbedIt CF names. If I hit a limitation, I’ll be back.

There are more plugins that require shortcodes than EVP and EmbedIt, both of which may be more obscure to the general public.

Off the top of my head, I can think of two plugins for which I own developer licenses that have employed shortcodes in posts/pages to render that content. Those two are Gravity Forms and Soliloquy.

Thanks for your reply, Daniel. I’m sorry it took me so long to find the email notification.

I’m afraid I’m not following your latest suggestion. Are you saying that I should add that script to the Gravity Forms Default Confirmation within the WordPress dashboard? Or, are you saying that I should update the script that I’ve already embedded in functions.php for the confirmation?

For the record, I tried a simple test of adding the script as a text confirmation to a duplicated form and it didn’t appear to work.

I hear you on holding out hope that Gravity Forms will respond. I opened a ticket with them near our around the time that I first put in a support request to you and it took them over a week to reply. Their reply simply asked me to restate what I had already told them.

P.S. When I set up a dummy Gravity Form with confirmation of page redirect using merge tags to pre-populate the destination form fields, neither Google or Chrome block the process on form submit.

The solution we discussed in email was not the solution that was implemented at the site. After learning how Gravity Forms constructed a link for a form using Merge Tags, I came up with this:

/* Redirect link after VIP Form Confirmation
 * Ref link: https://docs.gravityforms.com/gform_confirmation/
*/
add_filter( 'gform_confirmation', 'custom_confirmation', 10, 4 );
function custom_confirmation( $confirmation, $form, $entry, $ajax ) {
    /* VIP Quick Qual App */
    if( $form['id'] == '7' ) {
    $fname = rgar( $entry, '7' );
    $lname = rgar( $entry, '8' );
    $phone = rgar( $entry, '2' );
    $email = rgar( $entry, '3' );
    $redirect_url = rgar( $entry,'5');
    $goto = $redirect_url . '/?first_name=' . $fname . '&last_name=' . $lname . '&phone=' . $phone . '&email=' . $email;
    $confirmation =
                "<script>
                    /**
                    * Here you can simply change 132 to match your Popup ID #.
                    * The cookies settings will be determined the settings in the editor.
                    * Any trigger ( auto open, exit intent or scroll triggered ) that is
                    * Set to manual will have its cookie set using it's unique settings.
                    */
                    jQuery('#popmake-132').trigger('pumSetCookie');

                    /**
                    * Close the popup after a 2 second delay.
                    */
                    setTimeout(function () {
                    jQuery('#popmake-132').popmake('close');
                    }, 500) // one-half second
                    window.top.jQuery( document ).ready(function() {
                        window.top.jQuery(document).bind('gform_confirmation_loaded', function () {window.open('$goto{$entry['10']}');});
                    });
                </script>" . 'Thank you for completing the form.';
    }
    /* VIP Finance App */
    elseif( $form['id'] == '8' ) {
    $fname = rgar( $entry, '7' );
    $lname = rgar( $entry, '8' );
    $phone = rgar( $entry, '2' );
    $email = rgar( $entry, '3' );
    $redirect_url = rgar( $entry,'5');
    $goto = $redirect_url . '/?first_name=' . $fname . '&last_name=' . $lname . '&phone=' . $phone . '&email=' . $email;
    $confirmation =
                "<script>
                    /**
                    * Here you can simply change 137 to match your Popup ID #.
                    * The cookies settings will be determined the settings in the editor.
                    * Any trigger ( auto open, exit intent or scroll triggered ) that is
                    * Set to manual will have its cookie set using it's unique settings.
                    */
                    jQuery('#popmake-137').trigger('pumSetCookie');

                    /**
                    * Close the popup after a 2 second delay.
                    */
                    setTimeout(function () {
                    jQuery('#popmake-137').popmake('close');
                    }, 500) // one-half second
                    window.self.jQuery( document ).ready(function() {
                        window.self.jQuery(document).bind('gform_confirmation_loaded', function () {window.open('$goto{$entry['10']}');});
                    });
                </script>" . 'Thank you for completing the form.';
    }
    return $confirmation;
}

This is imperfect, however. Google is treating the resulting link as if it is a redirect and browsers (Firefox and Chrome) are blocking that transition to the form where the fields are supposed to be pre-poulated.

When the so-called popup from the constructed link is authorized in Firefox, the process completes and the form fields are properly pre-populated. Chrome doesn’t behave the same way. On a mobile (Android) device using Chrome, it just works.

Before I close this topic, I’d like to better understand why your plugin doesn’t see a form confirmation with merge tags as being a Gravity Forms Success on submit. You alluded to that in your email response but you didn’t fully explain the “why” of it.

I guess I found a workaround for this issue but it isn’t really pretty. I haven’t applied the fix to the site link I provided above yet but I have it working locally in Xampp.

I had to add this code to the theme’s functions.php file:

add_filter( 'gform_confirmation_7', 'custom_confirmation_message', 10, 4 );
function custom_confirmation_message( $confirmation, $form, $entry, $ajax ) {
    $confirmation = 'Thank you for providing your information.  You will now be redirected to the page you requested' .
                    "<script>
                    /**
                    * Here you can simply change 967 to match your Popup ID #.
                    * The cookies settings will be determined the settings in the editor.
                    * Any trigger ( auto open, exit intent or scroll triggered ) that is
                    * Set to manual will have its cookie set using it's unique settings.
                    */
                    jQuery('#popmake-92').trigger('pumSetCookie');

                    /**
                    * Close the popup after a 2 second delay.
                    */
                    setTimeout(function () {
                    jQuery('#popmake-92').popmake('close');
                    }, 2000) // 5 seconds
                    window.self.jQuery( document ).ready(function() {
    window.self.jQuery(document).bind('gform_confirmation_loaded', function () {window.open('https://localhost/drivelawrence/quick-qualify/{$entry['10']}');});
});
</script>";

    return $confirmation;
}

The confirmation message encoded into that function doesn’t ever appear but the cookie does get set according to the settings setup in the plugin.

I referenced this link for to enable the script method on a cookie:
https://docs.wppopupmaker.com/article/225-close-popup-and-create-cookie-after-gravity-forms-submission

I referenced this link for help with the Gravity Forms part of the script:
https://docs.gravityforms.com/gform_confirmation/#3-output-script-with-confirmation-message

It appears that I will have to create different forms for each navigation link using this method. I guess WP Popupmaker only will present a popup on a nav link but it doesn’t go beyond that to make the nav link functional without the code.

forget it

Caleb … I’ve been struggling to understand how to affect the number of products displayed per row. I did use the Appearance > Customize > WooCommerce feature to setup archives to display 4 products per row and 2 rows per page. I saved this setting.

The archive begins that way when I set it to display product categories but, if I click through on a category with more than one product, those are “totem-poled” in a single row. In other words, my theme supports the customize feature but the options for layout customization are limited and not taking when saved.

Another problem I’m having is the category image size on the archive. They’re HUGE and there is no setting in the customizer that targets category archive image sizes.

I’m using the Genesis Framework, a child theme. It is compatible with WooCommerce.

Well, the first admin account I setup had all the options without specifically selecting them so it must be some quirk associated with subsequent admin accounts.

Your solution solved my problem. I’ll try to remember that, should it come up again.

Gosh! It was so simple.

Any thoughts on why these must be specifically added for a second admin account on a site?