one3rdnerd

Just following up on this to see if others can replicate the issue. I think I notice it on every site.

Really? It doesn’t tell you that you aren’t using the keyphrase in the slug?

You did add a focus keyphrase right? You have to do that for it to analyze.

@maybellyne

In the reading settings, I have it set so the “Home” is the homepage and “Blog” is the Posts page.

That’s the correct way to set a static homepage and a page called “Blog” as your posts page.

Do you need any other info?

That’s a shame. I was excited to try this plugin but guess I’ll go back to Simple CSS/JS and Code Snippets.

Did you ever find a workaround to this? I have the same issue.

I also noticed CSS in admin only isn’t loading any CSS in the dashboard.

I’m also having this same issue.

Couldn’t you provide a setting to allow them to default as complete? Our donations are simply that, nothing physical needs to be fulfilled so they should be complete as soon as the donation is made.

Then users can choose to leave it as default if they need it or choose to have them set to status = complete if the donation doesn’t require anything else.

Our site sells physical products, which should be set to processing, but it’s confusing when donations show as processing.

I found a fix on https://github.com/woocommerce/woocommerce-paypal-payments/issues/1439 but I still think the plugin devs should resolve what causes this in the first place.

I found just disabling and resetting the smart button locations seemed to solved it. Maybe it needed to be reassigned for a woo-commerce database update

https://github.com/woocommerce/woocommerce-paypal-payments/issues/1439

Hi @saifislam01

Okay, sounds good. I appreciate it.

Do you have any plans to make your development roadmap public in the future?

Thank you, I’m glad you agree about the idea.

If you take my experience for example, when it wouldn’t change I thought it was either a bug or custom fields on custom posts simply were not supported by the plugin and nearly deactivated to try an alternative because it didn’t say “You can’t change the field after saving” anywhere, so I think it ended up being a poor user experience for a different reason.

I hope this gets implemented because while in the development phase of a website, it’s not too uncommon to change a meta key while working on the site.

Thanks ??

Thanks

Is this feature on your development roadmap for the future already? or if not, is it likely this will be added? I think this feature would put your plugin way ahead of the competition. I’d happily buy the premium version if this was included.

The answer is yes. I tested it.

Ah I found that if I add it when I first add the field without saving it works.

I think it should be editable after that though, if you are concerned about people breaking forms just show a “Hold on a second” popup to check the user definitely wants to change it and inform them of the potential issues.

@daanii11

Would you be open to sending me your custom plugin so I can try and adapt it to my needs? or point me in the right direction of the function you used?

Thanks in advance.