zavakz

Hmm, I believe I found the problem cause.

After switching “Hello Theme Header & Footer” to inactive under the Elementor Settings > “Features” it stopped showing the error. However I am not quite sure why it’s doing this as I went into the Site Settings and tried to change things to see if it stopped giving the error, but to no avail.

I think there’s a bug or error somewhere relating to this.

Thanks, I decided to use a redirect plugin instead, so I haven’t tested this, although I am sure someone else will find it handy.

I think something like this should be included in the plugin as it’s meant to be the complete package and having this page visible kind of spoils it.

Yes, I have that unticked, but as I asked specifically if this plugin also has the ability within the settings somewhere that disables or redirects the wp-login.php to the login page.

The “ultimate” had me assuming it was a complete package. For now I am using a redirecting plugin.

Hi, thanks, glad I could help.

I think I have narrowed down the issue to this script:

responsive\core\includes\compatibility\woocommerce\js\woo-floating-bar.js

Do you know how long a release would take to fix this? In the mean time is there a quick fix for this that one could do?

Hi @judagutor

Thanks, yes it worked perfectly fine with Storefront.

I switched off all plugins and still the issue was present so I do not believe it is a plugin or at least an active one. I restored the database to yesterday, I also wiped the theme folder and downloaded again, no luck.

I am using ‘Responsive’ theme by cyberchimps and it should be compatible with WooCommerce also I do recall it working as when I added the products to the group and gave it a test I did not notice it happening like this so I’m a bit confused. I was trying to add individual basket buttons to the group product page so maybe I broke something.

I just did a complete fresh install of WordPress and the theme, still the same issue happens so I guess the theme or at least the template is not compatible.

Any idea what I could look at on the theme? I know it’s not WooCommerce’s concern.

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

That is awesome, exactly what was needed.

Thank you.

Just to clarify, where exactly do I apply my own CSS or modify the silver?

I think you may have missed my point, when I add the plugin as a widget I do not see any option to choose say a custom image-style for me to then go and add custom css within my theme CSS files. Yes I could pick silver and add the modified CSS to my theme CSS file, but why have the first original silver be called for no reason.

Is there a function I can use to disable the default CSS?

Hi Mirko P.

Thanks for your response. I ended up using a database cleaner, randomly chose ‘Optimize Database after Deleting Revisions’ plugin and also using ‘WP Rollback’ I rolled back to 6.0.0 and tried to update again. I think I also tried to update to 6.1.0 and so it seemed to work so I never got a chance to follow your steps to narrow down if it’s the plugin acting up between those versions or my host timing out somewhere.

Either way, thank you for your help.

Hi @bvytis Thanks a lot.

I do have one question though. Is there a changelog page for Neve anywhere so I can keep track of the changes, I noticed there is an update and want to know the details before I update.

not sure how that would work. You are attempting to do a conditional mapping. This plugin has no conditional logic built into it. You could try with the Conditional Fields for CF7 plugin.

I’m not sure if we are misunderstanding each other here. For example if you create a untouched form by default it posts to a category, I simply meant the choice of which category the form automatically posts to could be under default post fields selection, just like the post title, featured image or the other ones that are included there.

You have to use the right one. You are trying to customise/change the post being saved after a form is submitted. If you read the description, only 1 hook fits that, #16.

Oh, I actually did not try that, the “after” part made me dismiss it, but thank you I’ll give it a go. I have been fixated on 8 & 9, and I assumed I should load which category it will post to in advance.

this has been superceded by the custom CSS editor which you can add to your form editor page. See the video tutorial. I will update FAQ #8 too.

All my forms have the same color and layout theme so the old way may be useful to some. I’d opt for keeping it.

don’t try to do that, you form will loose their grid layout styling.

Overall, I think you misunderstood me. I know one can add to the custom CSS of each form, but if they have one set theme for their forms, that’s not the best way to do it.

The plugin adds very few styling to the look of your form. Most of this is achieved by your theme.

Well like I said, for example your CSS stylings under cf7-grid-layout-public.css is pushing for the submit button background color to be grey and overlapping my theme CSS. I understand it needs to be a color if there is nothing set, but that was my suggestion about having an option to disable the additional CSS the plugin sets, if need be. Or maybe just like you have the option to create a custom CSS for each form, it could be a custom CSS for all forms.

Understood
So the plugin can’t do that automatically for you.

It would be lovely if it was listed along with the default post fields selection when mapping as it seems like the choice of category is a very common thing with posts.

This is a functionality that needs to be programmatically implemented using a hook.

Ok. I was more after being pointed in a direction such as what hook or where to begin. I’ve tried many on the list here.

I am not sure I follow you. What do you by 2 at a time?

Two of “post categories”..

I would like to quite simply specify what category the form posts to when it creates a post..

You mean this?

Yes and no. Like I mentioned, I can get it to be listed, but as I need to include also an option to choose a child category for the user, that takes it away from the list. As in I cannot use two at a time.

I was able to test out the upload feature without activating the pro trial version and I think it adds enough for any potential buyer to see what is on offer.

Regarding the pricing: It is my full-time job to develop this plugin and therefore the pricing level must be what it is, for me to make a living. The price has been lower before and I have gradually raised it when new features have been published. It’s been a bit over 2 years now that I have worked on this and I think the price is pretty fair, considered how much time I have used to build it. But I do understand that it can be too much and you have the right to state so.

Yes, you can tell someone has put effort into it. I think you may scare away potential buyers with such high price ranges, but I assume you’re right. Unfortunately it’s not quite what I want, as I was looking for the front end uploader to create and attach to posts, add or select tags (search bar rather than tick boxes) and for such a price I’d want it done already.

Anyway, thanks for your response and actually tweaking things to do what it says. I’m not sure whether to remove my review or leave it.