So yeah, new twitter api require oauth, so i decided to get rid of server side twitter feeds.
Right now twitter feed in the Ether Builder is powered by TwitterFetcher. Everything will look and work the same with one exception.
Instead of passing twitter username you have to pass twitter widget id now. Here is how you get it (text from TwitterFetcher’s page):
### HOW TO CREATE A VALID ID TO USE: ###
Go to www.twitter.com and sign in as normal, go to your settings page.
Go to “Widgets” on the left hand side.
Create a new widget for what you need eg “user timeline” or “search” etc.
Feel free to check “exclude replies” if you dont want replies in results.
Now go back to settings page, and then go back to widgets page, you should
see the widget you just created. Click edit.
Now look at the URL in your web browser, you will see a long number like this:
Use this as your ID below instead!
Patch will be available on CodeCanyon soon, in the meantime you can request this patch via email email@example.com
- fixed 500 internal server error
- Fixed: issue with thesis theme
- Fixed: Ether Builder takes into account password protected posts
- Fixed: Simplekey theme issue
- Fixed: Visual composer compatibillity
- Fixed: Rich Text
- Added: TED video support for video widget
- Added: Video support for Services widget (youtube, vimeo, ted, blip)
- Added: Start item position for sliders (Gallery, Testimonials, Services widgets)
- Changed: Documentation updates (mainly regarding custom CSS rules)
- Fixed: Navigation arrows getting partially cut off in Gallery Widget
- Added: Custom label for Rich Text widget
- Fixed: Rich Text widget error in sidebar widgets
- Fixed: jQuery 2.0 compatibility
- Fixed: Removed conditional ( ! user_can_richedit()) – rich text editor should be more stable now
- Fixed: “wp-includes/js/tinymce/langs/en.js 404” Error
- Fixed: Ether does not use built in get_called_class function as it caused too many problems in cases where 3rd party theme/plugin used own implementation of the function and ether assumed it to be a core function (Double from prev update)
- Fixed: removed deprecated wp_tiny_mce() function from builder.php
- Added: support for https protocol when including css/js
- Fixed: Error preventing from accessing form entries
- Fixed: Styling of entries sent via email
We are happy to announce that we have launched the new plugin – Ether Forms.
Ether Form Builder WordPress Plugin is a form building tool aided with visual composer allowing creation of complex form layouts easily. It comes equipped with all commonly used form elements as well as some extra widgets accessible via interactive Drag & Drop interface. No coding knowledge required. Ether Forms is an integral branch of Ether Content Builder – largely popular top content composer for WordPress.
- core changes
- minor ui updates
- Fixed: bug with generating wrong slugs (caused by sidebar widgets using wp_query and the_post when moving them from sidebars to builder)
- Fixed: Ether does not use built in get_called_class function as it caused too many problems in cases where 3rt party theme/plugin used own implementation of the function and ether assumed it to be a core function
- Fixed: Lightbox issues
- Added: Resave with the same name to update layouts
- Fixed: IE7 Columns issues
- Fixed: IE7 Form Fields issues
- Support for Post Revisions (beta) – it’s turned off by default and can be turned on in Ether > Builder > Enable revision support for Builder content
- Fixed: Scroll Spy issues
- Fixed: Conflicts with some theme/plugins interfering with searching posts for Ether Content Builder content
- Fixed: ‘output buffering’ issue causing fatal error
- Fixed: pods plugin conflict
- Fixed: Saving/Loading Ether Content Builder templates
- Fixed: Links in admin bar removed for users without proper permissions
- Added: Widget label (misc tab) – allows to provide custom title/label for a widget that appears in admin view (so you can have a widget titled ‘Image – custom image description’ rather than ‘Image – /path/to/image/or-other-cryptic-stuff’)
- Fixed: Warnings caused by changes applied to $wpdb->prepare() method in WordPress 3.5