saralovesyellow

Also worth mentioning that the Site Health tool does not work when Yoast is activated.

Hi! I too am using Divi and having similar issues. I cannot access the Divi Builder but i also cannot change several settings or create new users.
I switched to the TwentyTwentyTwo theme to troubleshoot, deactivated all plugins then reactivated one by one to find the naughty one…it was Yoast ?? I have tried rolling back to previous versions of Yoast but alas, the issue persists.

Hello, thank you for your quick reply.
All previously created folders are missing. I should have included that in the original post.
Thanks,
Sara

@dwaynecasey Unfortunately, we were not able to meet our needs with this plugin – not for lack of trying! We worked with the development team to try to fix various issues we were having but in the end we opted to get a licence for the UPS plugin offered by WooCommerce. I had very high hopes for this plugin and I think one day it might be an awesome resource for WooCommerce stores but right now (or at least a month or so ago) it just is not ready. Sorry I can’t give a better update or more guidance.

Depending on your needs it might be worth your time to reach out to the support team – they were very helpful and open to feedback. Even though they were not able to meet our specific needs with this plugin at this time- hopefully they can help you!

Hi Peter – thank you so much for your response and consideration of our issue.

If it is possible i do believe that the solution you have outlined will “fix” what we are experiencing. Please do keep me updated if this is a possibility ??

Thanks again and fingers crossed!
Sara

*marking as resolved*

Update: It turns out some other things were/are going on here. I do not believe it to be related to this plugin. Sorry for the trouble! Thanks!

Thanks all! After updating to 1.7.9 and a browser hard reload (ctrl+shift+R – ctrl+f5 didn’t do the trick for me) the builder is now loading properly again. Thanks again to everyone for the prompt reply, feedback and fix! ??

I am trying to save the value to the wp_usermeta table in the wordpress database using the Form Controls with Datasource connection and a custom query. Only the first portion of the value saves in the database (the date portion as described in original post).

Hello, thank you so much for your quick reply! Unfortunately this fix is not working when it comes to saving the value in the database. I am still only getting the same results in the database as previously (I am able to display a calculated field value in another calculated field using this method but that was never my intent – only something is discovered in troubleshooting the issue regarding saving the full variable to the database).

Is there something special I need to do with the variable in the query in order to save the full value?

Thank you again for your help,
Sara

I do understand that it would take some customization and is not a simple setting. Just hoping someone else has encountered a similar “issue”, created a solution and can point me in the right direction. Thanks again.

With the current shipping options we have set up, we would need to add 4 new shipping options with the $10 rush fee added in that will each need to be toggled on and off as needed. I would much prefer to worry about toggling a single item. I can go with the addition shipping options if that is what it comes to but what I am looking for is a way to exclude this single “product” from the free shipping amount.

The products are custom made, the “rush” option isn’t so much a shipping option as moving your purchase to the head of the production line.

Thanks your input so far folks!

Hi Mike, I am not sure I understand your meaning? Can you clarify a bit for me?
I should also mention the rush option needs to easily be toggled on and off (my current code allows for this by changing the product to a draft when rush ordering is not available).

Thanks!

Thank you! I did eventually figure out this was where to start. Working on bending the Attendees List to my will. Thank you again!

Thanks, Nick!

I actually stumbled upon that fix yesterday and intended to answer my own post this morning. Thanks so much for the reply!