I got rid of arrays (was planning to anyway, to get a better code structure) and it worked! For some reason I suspected that the use of arrays would be the cause. I just wasn’t sure of it.

Thank you so much!

Well I’ve tried the following:

get_theme_mod('my_theme_g_search_box_id', '1')
get_theme_mod('g_search_box_id', '1')
get_theme_mod('my_theme[g_search_box_id]', '1')
get_option('my_theme_g_search_box_id', '1')
get_option('g_search_box_id', '1')
get_option('my_theme[g_search_box_id]', '1')

But none of them has worked. The div is still visible no matter the option set and no errors reported.
Is there one I missed or something else?

Thanks

• This reply was modified 3 months, 1 week ago by maxlefou.

Wow that looks like a super great tool actually :O Doesn’t resolve the main problem but that can help people keeping the DuenaRevival theme updated more easily ^^

Thanks for the info, i’ll try on that!

Yes, this is what I meant.

So far, in the plugin, you can add a new custom tag or use an existing custom tag and add a value to it, as expected. But, when you do this, there’s no way to make wordpress save the changes without saving the whole page.

So, my idea is to add a “save” button (kinda more close than what i meant) which saves the added/edited tag and its value, then adds another new line to add/edit another custom tag and its value.

Sorry for my bad english, i’m not english native, i’m not sure I wrote it right.

• This reply was modified 10 months, 3 weeks ago by maxlefou.

Btw, dear developper, I’ve made a pull request that fixes the problem i’ve mentionned. Feel free to check out and review it!