Ability to edit sites snippets, CSS etc in one place over MainWP where WPCodeBox are installed.
13
It would be easy for users to see a check icon next to the cloud snippets that were downloaded to the current site.
1
It would be useful to add colors to folders in order to visually identify them quickier.
1
Please add an option to combine multiple files. For example, if I have 10 SCSS snippets I don'tΒ want toΒ have 10 separateΒ files.
2
As I personally transition from the Code Snippets plugin, one thing I'm finding that I'm missing is the ability to import/export snippets. This is important for ease of distribution to clients/customers that are not necessarily using WPCodeBox...yet. ; ) This goes hand in hand with the Add the ability to save CSS/JS to file feature request.
9
Add a GitHub connector so that users can save cloud snippets to GitHub instead of the WPCodeBox cloud account.
1
This would be useful for creating SQL snippets that you can run on the WP database and see the output. The implementation would include autocomplete for MySQL table names and column names to help write SQL code. An advantage of adding this would be that you could save your most-used SQL Snippets to the Cloud and share them across sites.
0
Add a way of debugging code snippets, and outputting variables during execution.
0
Use OpenAI Codex to generate WordPress Code Snippets using natural language.
1
Its pain to go trough every site and manually download updated snippets.
2
Visual editor options to enhance the user experience. On small screens the three columns cause the space for the code editor to be quite small. Enable option to occupy the available layout width. Enable option to expand editor to full screen. Enable option to edit without distractions.
1
Revisions history would be very useful, especially for css. Also a trash folder, in order not to lose anything by mistake.
3
Use a better editor for the Theme Customizer.
3
Detailed and updated documentation is an evidence of a great product. It will help everyone, from existing customer to potential customer. It may also help reduce the need of direct support, since everything (as it should) might be found in the documentation. A written documentation is preferred, and please consider to add images in it, so the user is quick to understand how to put what in where. Based on what I've seen, other snippet plugin (Code snippets pro, AS) lack in this area, only SCORG that already have much better documentation (though there are still lots of room for improvement there). It just sad that WPCB have so much nice features, but the documentation is sucks. I want to believe that WPCB is a product for everyone, ranging from expert devs to someone who eager to learn on how to code better by utilize everything WPCB provide in its arsenal. But until then, WPCB looks like a niche tool rather than essential one. Thank you.
0
I use libraries on my snippets quite often. And most of them have multiple files, like the SleekDB library. Whenever I need to use one, I have to manually upload the library to the file system and require it on my snippet. What is a pain in my case is that I have to re-upload the library each time I use the snippet on different websites. It would be convenient if WPCB could help us manage PHP libraries :) Maybe a separate category than Snippets called Libraries with its cloud counterpart? We can upload folders that will be stored on the file system that we can then require and use on snippets.
0