13 versions

Dynamic Content For Elementor history.

Every release of Dynamic Content For Elementor is archived here with its changelog, file size, and security scan result. Use the archive to roll back to a stable release or audit what changed between updates.

11 of 13 releases scanned clean

v3.4.11Latest

July 13, 202610.2 MBScanned

v3.4.10

June 17, 202610.2 MBScanned

v3.4.9

June 2, 202610.2 MBScanned

v3.4.8Unavailable

June 1, 202610.2 MBScanned

v3.4.7Unavailable

April 2, 202610.2 MBScanned

v3.4.6Unavailable

March 13, 202610.2 MBScanned

v3.4.5Unavailable

March 6, 202610.2 MBScanned

v3.4.4Unavailable

February 11, 202610.2 MBScanned

v3.4.3Unavailable

February 6, 202610.2 MBScanned

v3.4.2Unavailable

February 6, 202610.6 MBScanned

v3.4.0Unavailable

January 23, 202610.2 MB

Fixed

URLs are now resolved correctly based on https://datatracker.ietf.org/doc/html/rfc3986#section-5.2. #289
Absolute URLs with a path in a service description will now properly override the base URL. #289
Parsing a query string with a single PHP array value will now result in an array. #263
Better normalization of the User-Agent header to prevent duplicate headers. #264.
Added `number` type to service descriptions.
empty parameters are removed from an OAuth signature
Revalidating a cache entry prefers the Last-Modified over the Date header
Fixed "array to string" error when validating a union of types in a service description
Removed code that attempted to determine the size of a stream when data is written to the stream
Not including an `oauth_token` if the value is null in the OauthPlugin.
Now correctly aggregating successful requests and failed requests in CurlMulti when a redirect occurs.

Other

The new default CURLOPT_TIMEOUT setting has been increased to 150 seconds so that Guzzle works on poor connections.
the Content-Type can be determined based on the entity body or the path of the request.
The bundled SSL certificate is now provided in the phar file and extracted when running Guzzle from a phar.
You can now send any EntityEnclosingRequest with POST fields or POST files and cURL will handle creating bodies
POST requests using a custom entity body are now treated exactly like PUT requests but with a custom cURL method. This
means that the redirect behavior of POST requests with custom bodies will not be the same as POST requests that use
POST fields or files (the latter is only used when emulating a form POST in the browser).
Lots of cleanup to CurlHandle::factory and RequestFactory::createRequest

Added

a feature to EntityEnclosingRequest::setBody() that will automatically set the Content-Type of the request if
the ability to overwrite configuration settings in a client when grabbing a throwaway client from a builder.
support for a PSR-3 LogAdapter.
a `command.after_prepare` event
`oauth_callback` parameter to the OauthPlugin
the ability to create a custom stream class when using a stream factory
a CachingEntityBody decorator
support for `additionalParameters` in service descriptions to define how custom parameters are serialized.

Why archive

Sometimes the latest release isn't the one you need. The archive lets you pin Dynamic Content For Elementor to a known-good version, or roll back while a bug is investigated. Every release stays scanned and reachable.