e-DeveloperDEMO
Latest Wordspress.org News
Nice Trick to Clean Old Entries
Mike has posted a great SQL trick to the forums. Old versions of b2 would naïvely enter break tags (<br />) into the database, often breaking block-level code posted or just making formatting awkward. Now that WordPress has the autop function to intelligently add line breaks what do you do about all of your legacy b2 content? Mike (who has entered his sixth month of not smoking, congrats!) offers this quick query: UPDATE wp_posts SET post_content = REPLACE(post_content, '<br />', ''); Of course you should always backup your database before doing such an operation.
Post / Edit and Permalinks
I’ve been working on two new features that I have personally wanted for a long time and is now available to WordPress users currently through the CVS and eventually through a release. First we’ve separated the post and edit screen. The post screen now has just the form for creating a new post. There is a new edit option on the menu that has a page for recent posts and a page for recent comments. This makes things much faster loading and more efficient. The second change is with regard to permalinks and their structure. You can see these in action […]
0.72 Final Version Available
I am very happy to announce that 0.72 is now available. Here are some of the new features: An important security fix Tons of bug fixes Password protected posts Cursor-aware quicktags (like using a fancy text-editor) Improved API support: full or near full support for the Blogger, MetaWeblog, and MT APIs New template design from Dave Shea New configuration method, no more editing files! New Blogger import Improved upgrade and install scripts. Improved post and edit interface RSS feeds for comments RSS feeds support Conditional GET Improved XHTML auto-formatting Improved Link Manager Geographical data support Improved image upload features Improved calendar […]
0.72 Release Candidate 1
It’s available in the usual place, we need quick feedback on this. This release adds several new features and fixes an important security vulnerability. Unless any major bugs are found, this release will be identical to the final 0.72 release.
Pagination
Paginate in case of huge items number
POST Request
Send Post payload data on your request call
WordPress Rest API
Full support to native API
ElasticSearch
Full support to Elastic API to read Documents
Query Rest API
EndPoint URL
The remote url of API service
Require Authorization
Optional User and Password or Token access for private area
Port
Set if different from default 80
Connection Timeout
Sometimes the service could be longer than standard timeout
Ignore certificate
Enable it if remote service is not on ssl
Method
Many ways to manage request data and manipulate the response, some generics like standard GET and POST and more specific for WORDPRESS and ELASTICSEARCH
Parameters
GET & POST extra arguments
If you need to pass more data into your request, like authentication info, filter values, etc, you can add them defining for each one its own key accepted by the service and its value, maybe loaded via Dynamic Tag
WordPress Native API REST
Post Type
Set here the name of your CPT or leave default posts visualization.
Also different object types are supported, like “users”, “categories” and so on
Load Fields
By default you get only the ID of related post objects, like:
- Author
- Feature Media
- Categories
- Tags
Enable them to get full data of those object.
WARNING: this will increase load time, because each object require an extra request to WP remote service
Elastic Search
DSL
You can write your custom Query DSL (optionally dynamic with Twig), copy it from Kibana and execute here
Remove Quote
Optional, clean _source data from extra quotes added by elastic response
Load Document ID Object from Fields
Enable it to retrieve full data of main fields referenced only by Document ID.
Specify all fields, once per line, you want to fill with full data. Separate sub keys with a dot.
Level Depth
Maybe you need to expand fields of loaded documents nested on main document, so define how many iteration recursion you want to execute
WARNING: this will increase load time, because each Document require an extra request to Elastic remote service
Archive Rows
Archive Array Sub path
Set here optionally the index of sub array into the JSON result, separate each level with a dot
Rows per Page
Define how many result per page, necessary if activate the Pagination
Offset/Limit
Optional to modify the results display number
Cache
You can optimize page load with Enable Cache which will be valid for a defined amount of time until it will be refreshed.
Rest API Fields
We wanted to create a way to visualize, sort, and manage every type of data into the spreadsheet to generate complete lists in all its parts.
Display elements
- Custom Field, a column field
- Static (text, image, icon, code)
- Loop Index
- A custom Elementor Template
Each type of element is customizable in all its parts with dedicated parameters in order to achieve maximum control.
Style
All configurations for the style are accessible immediately while creating the items.
Advanced
As if that wasn’t enough, some advanced parameters let you refine the visualization and its behavior.
Query Rest API
SKINS
Several display styles are available for all e-Query widgets that will allow you to get the navigation approach you want.