Forum Replies Created
-
Replies
-
That’s awesome, @iphoenix. Thank you for making your options available. I’ll review and see how they fit into the child theme we are building. Are you open to taking on a few development tasks?
@david-wpck, nice to hear from you. I think it’ll be fun to work on and we’ll have something we can all use when we’re done. Jump Start is awesome and I am looking forward to collaborating with others that use it. I’m sure we’ll all level up our skills up because of it.
Onward!
Brilliant! That is more than what I was expecting. I can’t wait to use it.
Thank you, Jason for continuing to make Jump Start better!
Hey magicss,
The Events Calendar by Modern Tribe works really well and we have used it on Jump Start and other ThemeBlvd themes without issue. http://tri.be/shop/wordpress-events-calendar/
Cheers!
Scot
Hello askwpgirl,
I had a similar requirement recently to alter the grid columns and this is what worked for me. This one is for a specific post type but you get the idea…
// conditionally modify the number of grid columns function rum_member_grid_columns() { // set the number of columns for the member archive page if ( is_archive() && 'members' == get_post_type() ) { return 4; } } add_filter( 'themeblvd_default_grid_columns', 'rum_member_grid_columns' );For two columns, you may need to
return 6;. I think that will give you a 50/50 layout. Give it a try!Yes, that’s right. I was able to upgrade after reactivating the license. The error (#post-13945) is still coming up even after the upgrade. I don’t know why that is coming up. Would it be related to the renewal? I see two entries in my account for the same license but with different purchase dates. There is also a second license in my account, making for three purchase entries and two unique licenses. Do you think the second license may be tripping it up?
Production: I checked two production websites that were on v1.1.2 and I wasn’t getting the update notice on either of them. I removed the license and saved the page to clear out the field, then reactivated it again. Once I did that, the upgrade notice appeared and I was able to upgrade. The production sites do not have debugging on so I could not see if the same error was coming up or not but there wasn’t an option to upgrade until I reactivated the theme license.
Development (WAMP): After reactivating the licence, I was able to update. The error is still there but maybe it is unrelated since reactivating the license enables the update.
I checked the server log this morning and this may reveal a bit more:
[30-Dec-2013 10:56:25 UTC] PHP Notice: Undefined index: path in C:\wamp\www\local-dev\wp-includes\class-http.php on line 809 [30-Dec-2013 10:56:25 UTC] PHP Stack trace: [30-Dec-2013 10:56:25 UTC] PHP 1. {main}() C:\wamp\www\local-dev\wp-admin\themes.php:0 [30-Dec-2013 10:56:25 UTC] PHP 2. wp_prepare_themes_for_js() C:\wamp\www\local-dev\wp-admin\themes.php:90 [30-Dec-2013 10:56:25 UTC] PHP 3. get_site_transient() C:\wamp\www\local-dev\wp-admin\includes\theme.php:395 [30-Dec-2013 10:56:25 UTC] PHP 4. apply_filters() C:\wamp\www\local-dev\wp-includes\option.php:1030 [30-Dec-2013 10:56:25 UTC] PHP 5. call_user_func_array() C:\wamp\www\local-dev\wp-includes\plugin.php:199 [30-Dec-2013 10:56:25 UTC] PHP 6. EDD_SL_Theme_Updater->theme_update_transient() C:\wamp\www\local-dev\wp-includes\plugin.php:199 [30-Dec-2013 10:56:25 UTC] PHP 7. EDD_SL_Theme_Updater->check_for_update() C:\wamp\www\local-dev\wp-content\themes\jumpstart\framework\admin\updates\class-edd-sl-theme-updater.php:76 [30-Dec-2013 10:56:25 UTC] PHP 8. wp_remote_post() C:\wamp\www\local-dev\wp-content\themes\jumpstart\framework\admin\updates\class-edd-sl-theme-updater.php:103 [30-Dec-2013 10:56:25 UTC] PHP 9. WP_Http->post() C:\wamp\www\local-dev\wp-includes\http.php:195 [30-Dec-2013 10:56:25 UTC] PHP 10. WP_Http->request() C:\wamp\www\local-dev\wp-includes\class-http.php:291 [30-Dec-2013 10:56:25 UTC] PHP 11. WP_Http->_dispatch_request() C:\wamp\www\local-dev\wp-includes\class-http.php:192 [30-Dec-2013 10:56:25 UTC] PHP 12. WP_Http_Streams->request() C:\wamp\www\local-dev\wp-includes\class-http.php:266The theme is activated. There is a green “active” area on the theme license page. I turned on the debugger and I am seeing this error at the top of the /themes.php page: http://screencast.com/t/eLmI3njpFVBT
It looks like it may be related. It references EDD_SL_Theme_Updater in the middle of the call stack. Is there a chance this is getting in the way of checking for an update?
UPDATE: Trigger nesting
This was a bit tricky but I got it to work. The field that is nested, doesn’t need to receive for the first option, just the second option. The second option does need the trigger class. All other fields need to receive for all possible options. This is a compounding effort and can get really complex, really quickly. It may not be ideal but it does work within the framework. It may be recommended to write custom JavaScript for more complicated interfaces.
Jason and @Bluenotes…Thank you both for working out this issue with me. After adding a unique ID to the subgroup end, it is working great. I also added another subgroup to the same page and both of them are working perfectly. It appears that each subgroup start and end array not only needs an id, it must be unique.
Next, I’m going to attempt to nest a subgroup within another. 😉
Cheers!
Thank you @Bluenotes. You’re on to something. I added an ID to the subgroup and that enabled the show-hide-toggle to work properly but it also broke the page style a bit and now the theme option tabs to the right of Style are blank. Something isn’t getting closed properly.
Here is a screenshot of the theme option sections within my Styles tab. You can see they aren’t breaking properly.
http://screencast.com/t/yUasvT6zsuKlThis screenshot shows the tab(s) to the right of Styles are blank.
http://screencast.com/t/uiXrEjvgm@Bluenotes, did you have to add anything to the closing array?
array( 'type' => 'subgroup_end' )
The trigger is working but something still isn’t quite right.
