I’m not entirely sure why a standalone theme wouldn’t include all the child theme files. What you’ve described sounds a lot like what would occur if you created a new child theme in Runway and didn’t add any custom theme files. The Runway framework is only going to add the absolute minimum files required to generate a WP child theme, nothing more unless you tell it to. This leaves the entire process of theme design and development in your control to create exactly what you want, how you want.
If you’ve added custom files to the child theme and they are not being included in the standalone theme, let me know! I want to look into that right away because it shouldn’t happen and we’ve never seen that happen. That’s a bug we will drop everything to investigate and fix.
If you have more details about the process you’ve followed and what is occurring that will be very helpful and we will do whatever we can to ensure you get your theme working.
We have a support forum dedicated to Runway on our website where you can post questions, issues and other requests. There’s also a GitHub repository where you can post issues. Let us know how we can help and we’ll do it!
We support WPML already in the current version. It was a big priority for us in the last few months as well as a big push for translations. We have a bunch of new translations completed now such as Spanish, Romanian, German, Russian, Japanese, Ukrainian, Polish and French.
There will be more translations coming as well. We’re trying to find someone that can help with Italian, Portuguese, Dutch, etc…
Themes will continue to be compatible with WPML so long as they follow the WordPress standards for including translation strings with the __() and _e() function wrappers. It’s a pretty simple thing to do and most developers remember to do this. All of the framework generated code is output with these wrappers and is included in translation files.
I found the problem. It was a memory issue caused by the size of the theme directory. There were several large Photoshop files in the theme. Once they were removed I was able to create a standalone package.
I have installed some extensions (layout manager etc…) and have no idea where to use them as no new options have appeared on my child theme set up via runway.
Do you know why this might be happening?
Thanks!
*** wow im blind i just found it under appearance ***
Some extensions are added to specific WordPress menus based on functionality. We probably need think about adding a visual indication when these menu items are first added. Especially if they exist in sub-menus of existing WP locations like Appearance, Settings, etc.