e-DeveloperDEMO
Latest Wordspress.org News
WordPress Summer of Code 2009
Dad: Well, Billy, another school year is coming to a close. No more college parties, just another summer here at home. What will you do all day? Billy: Oh, I dunno. I’ll probably work on my blog or something. Dad: You need more direction! That blog is just your generation’s answer to comic books. Billy: […]
Contributing to WordPress, Part I: Development
A week or two ago at WordCamp Denver, I gave a presentation about some plans to create more opportunities for people to contribute to the WordPress open source project. The icon design contest was such a success that it seems clear we need to come up with ways for non-developers to contribute their talents and […]
Change the Web Challenge
We’re excited to be part of the Change the Web Challenge. Basically, the contest is to create a plugin, widget, mash up, hack, or other variety of web application that helps people find and share opportunities to take action. The grand prize is 50 benjis, and the best WordPress plugin will also be featured in […]
New and Improved Plugins Directory Search
One of the biggest problems and most frequent complaints we’ve had with the WordPress.org Plugins Directory is the horrible, horrible search results. No longer. We’re now using Sphinx (a “free open-source SQL full-text search engine”) to power search on the Plugins Directory both from the website and from within your blog’s admin (Plugins → Add […]
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.