Sherrie Brittig

Thank you–that worked! And thank you for the links to the courses!

Thank you!

Thank you–that worked nicely! Suggestion for getting rid of the “showing single result” message and improving spacing between Canal pic and caption?

https://www.sherriebrittig.com/product-category/classes/

This topic is of interest to me, since I will have live classes for purchase, and jewelry in different collections. If I understand correctly, instead of making a separate shop page for the classes and each of the jewelry collections, I can instead create categories that could be chosen from a drop-down link or menu, for example, that will show up as their own page although actually part of the one shop page? Is that right?

I’m not sure why I couldn’t log in. What happened: I brought up log in page for WP admin after upgrade of plugin, my username and password were saved and auto-entered. I hit submit to log on, but the page refreshed with my username and password blanked out. I manually typed in both, hit submit, and the same refreshing and blanking out of fields occurred. It simply would not recognize my log in info. After deactivating and reinstalling 3.0, the login worked again. Wish I could be of more help here.

Thanks for the instructions on code editing–Worked, and my site is showing secure again!

I rolled back to 3.0, and can now get into Dashboard. But my site no longer shows the green lock, just the nasty red slash through the HTTPS. I don’t know if this is a problem on my end, or a result of deactivating 3.0.1 and rolling back. When I check Force SSL Exclusively in my HTTPS Settings, I get the message SSL Admin – FORCE_SSL_ADMIN and FORCE_SSL_LOGIN can not be set to true in your wp-config.php.

Do I need to edit wp-config.php, and if so, what do I add or delete?

I loved this plugin when using 3.0 previously, and want it to work again. Will upgrade to 3.0.1 when the admin login bug is fixed.

I am having the same problem–it won’t recognize my username and password, and I can’t log in to my Dashboard. I’ll remove it from my plugins, and see if that solves it (can I roll back to the former version, though?)