excentricjester

I just noticed a JS error in the console and updated the code to the below and that worked as expected.

on_sent_ok: "__gaTracker('send', 'event', 'store-contact-form', 'submit');"

Sorry, I was sure I checked it and it was using ga() in the analytics code.

on_sent_ok: "ga('send', 'event', 'store-contact-form', 'submit');"

This site is using WooCommerce Google Analytics Pro to add the analytics code and I saw the same issue on another site using GA Google Analytics with universal analytics option.

I found a solution using the below, but it would be good to know why the normal redirect didn’t work for categories.

For anyone looking to implement the same it’s important to list any sub-directories first.

<IfModule mod_rewrite.c>
    Options +FollowSymLinks
    RewriteEngine On
    RewriteRule ^product-type/accessories https://newsite.com/product-category/accessories/child-category [R=301,L]
    RewriteRule ^product-type/accessories https://newsite.com/product-category/accessories/ [R=301,L]
</IfModule>

Sorry uxarax, after 2 weeks of contacting Salient theme support I never got this resolved and because of the project deadline and time invested in editing the theme I had to use a different membership plugin that didn’t use redux which was a shame because UM looks awesome!

I had a private ticket with Salient, but they said “both the Salient Options Panel and Ultimate Member Admin seems to be working and I can see no console error in the browser”… they mustn’t have been looking very hard and I had even supplied quite a few screenshots of the issues.

There’s a Salient Theme Facebook group where you might be able to find some help. A few people said they were running UM and Salient together successfully, but they were using Salient 6.1.72

Thanks for the quick update again Chad! Great support ??

Sorry, I updated my previous reply because while it was working it was linking to a different api.php file.

You might be in the wrong repo. Check github.com/butlerblog/wp-members/tree/master/admin/includes

To fix your site for now you can upload the missing api.php file from the Github repo.

I’m sure Chad will update the plugin soon!

I’m seeing the same error with debugging turned on. The entire admin returns a 500 error unless wp-members is removed from the plugins directory.

Thanks for the quick update!

I might remove the filter and try to work out the issue if it arises again.

I should point out that I’m using the fallback CSS with the code below, because the icons were not loading from the CDN on a client’s iPad. I think it may have been related to using a protocol relative URL.

add_filter( 'bfa_force_fallback', '__return_true' );

I’m still trying to get this issue sorted out and I have been in touch with Salient theme support for the past week.

Is it possible to use UM with a theme that also uses the Redux Framework?

I was able to solve the field_upload.js 404 by making a change in the themes functions.php

from

ReduxFramework::$_url . 'inc/fields/upload/field_upload.js',

to this

NECTAR_FRAMEWORK_DIRECTORY. '/redux-framework/ReduxCore/inc/fields/upload/field_upload.js',

I’m still getting a 503 error on one server, but I’ll open that as a separate issue.

Oh okay, thanks! I’ll try to contact the Salient theme developer.

Looking at the pre-release of Ultimate Member 1.3.53 I can see select2.css and ace.min.js have been added, so just looking for field_upload.js to be added if it can.

I’ve just noticed this bug still exists in 0.9.6 (on WordPress 4.5.2 and PHP 5.3.29).

Descriptions appear to work fine in the lightbox for single images and in a gallery where every image has a description, but in a gallery where some images have a description and others are blank you can see the description text is not reset to be blank as it should.

To reproduce the issue:
1. Create a gallery with 4 images
2. Set image descriptions (1st ”, 2nd ‘foo’, 3rd ”, 4th ‘bar’)
3. Click through images in lightbox to see how description changes

On the first loop through the descriptions will be:
Image 1:
Image 2: foo
Image 3: foo
Image 4: bar

On the second loop through the descriptions will be:
Image 1: bar
Image 2: foo
Image 3: foo
Image 4: bar