Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Settings are not getting stored #224

Open
drsdre opened this issue Oct 20, 2021 · 3 comments
Open

Settings are not getting stored #224

drsdre opened this issue Oct 20, 2021 · 3 comments

Comments

@drsdre
Copy link

drsdre commented Oct 20, 2021

Starting with the latest update (v2.3.5), changes to settings are not getting stored anymore it looks.

Steps:

  1. Open the settings page.

  2. An admin notice states:
    WP-SCSS: Please save your settings with the Base Location of Current Theme specified.

  3. Change 'Base location' from 'Uploads Directory' to 'Current Theme'.

  4. Click on 'save'.

  5. A green admin notice status 'Settings are stored'.

Expected:
Base location changed to 'Current Theme'.

Actual:
Base location is changed back to 'Uploads Directory'. The admin notice "WP-SCSS: Please save your settings with the Base Location of Current Theme specified." is shown again.

Changing other settings like 'Development Mode' also are not persisted.

@shadoath
Copy link
Collaborator

shadoath commented Oct 20, 2021

It sounds like you are on v2.4.0 now.
What are the available options for the Base Location? Is there a parent or child theme?

Can you look at your DB and see what wp_options table shows for the option_name of wpscss_options?

@drsdre
Copy link
Author

drsdre commented Oct 22, 2021

Indeed v2.4.0 when it failed. Since then I reverted to 2.3.5 which at least made the parsing work again (but still no options are getting stored).

The Base Location options I have are 'Current Theme', 'Uploads Directory' and 'WP-SCSS directory'.

Unfortunately there is no 'wpscss_options' key to be found in the wp_options table (wp_6s23HE_options table actually).

Can I provide you with any further information?

@shadoath
Copy link
Collaborator

@drsdre did you get this working with a later update to v4?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants