semidivine

Thank you Dmytro, I have tried something similar and it didn’t work. I will try your code and report back.

Hi Patrick, thanks for replying.

I’m sorry I must have explained the situation unclearly. What I am asking is how to unenqueue any stylesheets that are autogenerated by your plugin in my uploads directory.

These are your styles that are loaded by your plugin in the footer of the page:

<link id="forminator-module-css-276-css" href="/wp-content/uploads/forminator/276_eed77a053e063ebb55fa9aba8ae60249/css/style-276.css">

<link id="forminator-icons-css" href="/wp-content/plugins/forminator/assets/forminator-ui/css/forminator-icons.min.css">
<link id="forminator-utilities-css" href="/wp-content/plugins/forminator/assets/forminator-ui/css/src/forminator-utilities.min.css">
<link id="forminator-grid-default-css" href="/wp-content/plugins/forminator/assets/forminator-ui/css/src/grid/forminator-grid.open.min.css">
<link id="forminator-forms-default-base-css" href="/wp-content/plugins/forminator/assets/forminator-ui/css/src/form/forminator-form-default.base.min.css">
<link id="intlTelInput-forminator-css-css" href="/wp-content/plugins/forminator/assets/css/intlTelInput.min.css">

The last 5, which load from your plugin (/plugins/forminator/assets/) are all good.

The first one, which is the only one that loads from my uploads directory (/uploads/forminator/), and is autogenerated, is the one causing the problem. I know it is autogenerated because I deleted it from my uploads directory and your plugin recreated it.

When I first installed Forminator locally I didn’t realize my WordPress site url was http. I saw the error “Forminator’s CSS style cannot be loaded because your website’s address is configured in WordPress to use HTTP instead of HTTPS. This may cause some web content, including Forminator forms, to display incorrectly” in the Forminator admin but I ignored it because the forms were looking great. The only stylesheet that was not loading because of not being on HTTPS was the one in the /uploads directory.

I spent a lot of time tweaking the form based on those original styles.

Then I realized my local site url was HTTP so I switched it to HTTPS and that /uploads directory stylesheet messed up my form. I tested all your built in style options Design Style > Default to Design Style > None and they all mess up my form.

I found the code in your plugin that was enqueueing that style (in /plugins/forminator/library/render/class-assets-enqueue.php, line 115):

/**
    * Load relevant module CSS
*/
protected function load_module_css() {
    if ( ! empty( $this->model->id ) && ! is_admin() ) {
        $id = $this->model->id;
        $timestamp = ! empty( $this->model->raw->post_modified_gmt )
            ? strtotime( $this->model->raw->post_modified_gmt )
            : wp_unique_id();

    // Module styles.
    wp_enqueue_style(
        'forminator-module-css-' . $id,
        self::get_css_upload( $id, 'url', true ),
        array(),
        $timestamp
    );
}

I know this is the code correct code snippet because I commented it out and that restored my original styles (and didn’t break the plugin!) Obviously it is unsustainable to comment out plugin code, I could never update your plugin.

The answer is to unenqueue this stylesheet in my theme’s functions.php, but I am having a hard time doing that with yours. Can you help?

Thanks for responding.

I was assembling a list of plugins for you and I realized I still had ‘Contact Form 7 – Dynamic Text Extension’ enabled, even though I wasn’t using it. I disabled it and now the variable is being passed. So you helped! Thanks.

I found this:

function custom_pre_get_posts_query( $q ) {
    $tax_query = (array) $q->get( 'tax_query' );
    $tax_query[] = array(
           'taxonomy' => 'product_cat',
           'field' => 'slug',
           'terms' => array( 'sale' ),
           'operator' => 'NOT IN'
    );
    $q->set( 'tax_query', $tax_query );
}
add_action( 'woocommerce_product_query', 'custom_pre_get_posts_query' );

but it only works because I added all the sale items to a category called “Sale” and it only works on the shop home page, not the category archives. If someone could help me extend this to the archives and/or edit it to select sale items without the category (more efficient) I would be most grateful.

• This reply was modified 6 years, 5 months ago by semidivine.

I solved this on my own! That always happens as soon as I’m frustrated enough to post.

Hey there! The host has updated the PHP version and the specs you specified (https://lucyschwartzmusic.com/info.php) and I am still getting the errors:

GET https://www.lucyschwartzmusic.com/http:/www.lucyschwartzmusic.com/plugins/nextgen-gallery/products/photocrati_nextgen/modules/lightbox/static/shutter/nextgen_shutter.min.js?ver=2.2.14 404 (Not Found)

The URL is still borked. What can we do here?

I just put in a request to the host, a couple of the specs were off. I will reconnect when they have those updated and let you know if the issue has resolved. Thanks!

Part of the problem seems to be the page is not recognizing the function.

I tried:

if (function_exists('get_wp_term_image')) {
	echo 'x';
}

x did not output on the page.

@photocrati…
I am using the most recent version of NextGen (Version 2.0.66.17)
I just did the cache clearing you suggested.
Then I checked the database and there is a new “post” created by NextGen from today:
https://tinyurl.com/nh4yfug
All the other db entries are also still there. I don’t understand what these are for and what is creating them. Can I just delete them?
Thanks again.

Good news!
Upgrading incrementally, and testing out each version worked! It’s also possible the upgrading straight to 2.0.66 manually might have worked as well. The auto updater must have left an incomplete version.

Anyway, thanks for your time.

Oh I thought I explained that in the interest of keeping a live site functioning properly I reverted to 2.0.11. So any link now would show you a functioning plugin.

But what I am planning on doing is upgrading to later versions of nextgen incrementally. Not all of them (there are so many!) but every 5 or so. I will let you know when I first encounter the problem.

FYI The theme we’re using is twentyfouteen.

I will try to manually reinstall 2.0.66 and I’ll let you know if I have the problems.

Gosh, I really don’t want to argue.

I am not thread-hijacking, all I was ever asking, in lieu of writing out my whole saga (which I will if I need to), is what was the solution you found for this guy because in all likelihood it may work for me?

The best practices I’ve been taught is to search in forums for my issue so as not to have 10 different threads about the same issue. Also it saves you time, doesn’t it, if one thread can solve a bunch of customer’s issues?

Anyway, have a lovely day.

It’s actually not a different issue! Except for the fact that I had not recently updated to 2.0.40 (my client was updating her own plugins so we don’t know when the issues started exactly) the ORIGINAL poster’s first two paragraphs:

– all gallery’s in all previous posts is not working, error message:
“Gallery not found. Please check your settings.”

But they are present in “Manage Galleries”.

– addidg a new gallery in posts by pressing button “AddGallery” shows screen with error in gallery selection part:
“Warning: Creating default object from empty value in /var/###/###/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/attach_to_post/mixin.attach_to_post_display_tab.php on line 236”

is IDENTICAL to my problem. Why do you keep saying they are different?

My only other ADDITIONAL problem, having “NextGen Basic Tagcloud” as my only gallery option is secondary, because it doesn’t actually matter what gallery options I have if the galleries don’t show up.

Is there any solution to the ORIGINAL poster’s ORIGINAL problems? Because they would help me too.

My problem was identical to the original issue listed above, so I wrote on this thread because I wanted to know if there was a resolution. If there was you resolved it privately without enlightening others!

Anyway, I backed up to an earlier version of Nextgen (2.0.11) and now everything is working. So there seems to be an issue from 2.0.40 on (I had the latest version.)

Let me know if you come up with a fix, and I’ll update again to the latest version.

Oh and what was with “NextGen Basic Tagcloud” being the only option to display galleries? That’s very strange. Is that intentional?