September 8, 2013 at 4:39 am #294
When creating a new theme option, for example a container, and check the box for theme customizer, it does not appear in it. Are we talking about the WP frontend customizer, right?September 9, 2013 at 4:16 pm #298
That should be working. Just last week we were looking at this for a different issue, but there weren’t any problems with areas not appearing. I think we might need just a little more information to track this one down.
Did you add a field to the container also so there was something to be shown? I’m not sure if it will show an empty container.September 9, 2013 at 4:35 pm #299
Thanks for your answer Andy!
What I tried to do for example, is to tick the theme customizer checkbox of the Logo container already created with the theme which did not work but after your reply I did try to create another container with the content of the logo one and it worked, go figure why it won’t with the original one. But although it works as it shows the options in the theme customizer, it is actually missing all the labels text and the select file option return an error and force the page to reload.
September 9, 2013 at 4:56 pm #302
- This reply was modified 3 years, 11 months ago by Le Dave.
The missing labels is exactly what we were looking into in the previous post, where I mentioned we had a different issue last week. We were not able to replicate the missing labels issue, but I think it’s a problem specific to this version of Runway.
One thing that might be happening is the default theme is WAY out of date now. We’ve done so much updating to Runway and the core options structure that I really need to do an update to Liftoff. It’s on my list for something that will probably happen in the next 2 weeks. We’re pushing hard to make some big progress to Runway over the next month so look for things like this to change.
What happens if you create a new child theme and add options? Do the “customizer” fields still have no labels?September 9, 2013 at 5:13 pm #305
I really appreciate the work you’ve done so far and I see a big potential to Runway, I like the idea behind it and I will be watching it closely. I am myself a theme developer with my own front-end admin framework but I strangely getting lazy and looking for a better way of to improve the dev process, and managing all theme in one place like it does with Runway seems to way to go.
Oh, to answer your question, yes same with a new child theme, no labels.September 10, 2013 at 9:49 am #309
Thanks for the follow up. I’m going to test this now. I’m thinking this might have been a problem specific to this beta version. When we tested it with the latest “nightly” release last week it seemed to be working.
We should be ready with a new release of the beta and a new public repository on Github any day now. If I could just get myself around to doing a review of the code and an “about” page it would be live already.
Thanks again for the feedback and I’ll see about getting an updated beta published until we can have that git repository available. Keep the suggestions coming.September 16, 2013 at 12:49 pm #312
Any update on this bug?September 16, 2013 at 1:11 pm #313
It seems to work in the latest version so it was specific to the currently available beta. I’m pushing out 3 big updates in the next two days for other projects but as soon as that’s done I’ll be returning to Runway issues and getting a new beta published.
You must be logged in to reply to this topic.