- New: Improved the documentation of the full screen button
- Fix: A change in 2023.3 broke the standalone version. This is now fixed in 2023.4.
- New: Real fullscreen. The setting fullscreen_button_full enables the browser fullscreen.
- New: fullscreen_button_hide_elements does now hide the elements by CSS and JavaScript. By CSS was not working e.g. for google ads as they have inline styles with !important that can not be overwritten.
- New: Added "Left top corner" and "Left bottom corner" to the selection for the fullscreen button.
- Fix: Added shortcode attribute to the description of fullscreen_button_hide_elements
- Fix: Added !important at the style for display:none that should hide elements in fullscreen mode when the button is used. This enables that is also works where !important is also defined at the element which should be hidden.
- Fix: iframe_url_id only shows an error now if the page is in an iframe and the mandatory parameter is not set.
- Removed: removed aiLoadExternalConfig from the external workaround. It was deprecated for 2 years now.
- New: Compatible with Wordpress 6.2 - The editor block was broken as Wordpress changed a internal structure.
- New: The fullscreen button was enhanced. You can now hide additional elements which are still over the iframe. See the documentation of fullscreen_button_hide_elements
- New: Improved documentation. Added "How to find the id and the attributes". where needed.
- New: Missing purchase code message is now shown as general message
- Fix: The Javascript minimizer changed their URL. Now the new one is used.
- Fix: During search the help page is fully available now. This enables, that the links to the help section works properly.
- Fix: auto_update_plugin filter was improved to not show a warning if "$item->slug" is not set.
- Fix: Deprecated message in printReferrerpolicy fixed.
- New: hide_part_of_iframe does now support position:fixed. This enables this feature also to work together with fullscreen iframes. Adding an f (position:fixed) in front of the zIndex has to be used to enable this.
- New: The CSP header detection is now checking next to SELF and NONE also for the domain itself at the frame-ancestors.
- New: The url/hash cache for rewrite urls can now be deleted in the administration if needed. Please note that this cannot be reverted.
- New: Improved documentation of "Prefix/id/urlrewrite for iframe URL". Contact the support for individual solutions.
- Fix: The disabling of the auto updater in the pro version was rewritten to the examples WordPress provided.
- Fix: aiModifyParent was loaded directly and on jQuery.ready. When loaded directly some elements are maybe not ready yet and an error was shown in the browser in console the .css is not a query function. Now this error is catched
- New: Tested with Wordpress 6.1.1
- Fix: "Undefined array key" warnings when updating to php 8.x. If the database does not contain the required values now defaults are stored always during activation. Before it was only saved if no values where present.
- Fix: hide_content_until_iframe_color was causing an "Too few arguments ..." error. This is fixed now.
- Fix: addAdminHeaderCode is now using getAiAdminOptions instead of get_option. This does then always load the defaults even when the data could not be loaded from the database.
- New: The HTML attribute refererpolicy is now available in the administration and as shortcode attribute.
- New: Custom attributes can be added on the basic attributes page and in the shortcode. The shortcode attribute for this is custom="". e.g. custom="data-custom='data1' data-custom-2='data2'" if you like to add 2 custom attributes. See https://www.tinywebgallery.com/blog/advanced-iframe/demo-advanced-iframe-2-0 for an example.
- New: Check all iframes is now also checking Gutenberg pages and display the page type in the tool-tip. Also normal HTML iframes are detected. So you can replaced them with advanced iframes.
- New: src which are only numbers are now marked as invalid in the "check all iframes" feature.
- New: Some themes like Twenty Twenty-Two required an additional p around the iframe to be placed properly. To render this element you can set now add_surrounding_p="true".
- New: Enhanced the documentation of the HTML property "allow".
- New: Enhanced registration message. The message cannot be removed permanently anymore as not all features are available anymore if have not entered it.
- New: Invalid purchase codes are removed and not only a message is shown.
- New: Enhanced sub domain documentation for the upcoming change in chrome 109 - see: https://www.tinywebgallery.com/blog/sub-domain-workaround-with-chrome
- New: Tested with Wordpress 6.0.2
- Fix: replace_query_data which is used in the placeholder replacement like param={query-param} was using a non static method in a static context. This is not supported since php 8.0 anymore. This was causing a "Fatal error: Uncaught Error: Non-static method ... cannot be called statically" error.
- Fix: The standalone version file was missing a "," in the settings section that made the whole version failing.
- Fix: check_iframe_batch_size new default is now 20 as the 100 before was not reliable enough.
- Fix: The link in the registration message was linked to the wrong part of the options tab. Now it goes directly where you can enter the purchase code.
- Fix: When saving a post the url was not checked even it was not enabled. Now ai_checkUrlStatus is called properly when the classic editor is used.
- Fix: The WordPress theme Twenty Twenty-Two evaluates shortcodes before the body only. The advanced iframe pro optimization to prevent this leads to the issue that the iframes are not shown there! The optimization is now disabled by default and can be enabled on the options tab at "Technical options" -> "Prevent early shortcode execution". At the description you find the instructions how to check if the optimization will improve your site.
- Fix: When the setting loading (default HTML lazy loading) to false the loading HTML attribute was still rendered. Now it is not rendered anymore like described in the documentation.
- Fix: In 2022.3 the optimization for the timeout was containing a bug for the resize. This is now fixed.
- Fix: aiRemoveFile does now also have a nonce and the check for it. This is no security issue as deleting an already deleted file causes no problems.