If-So Dynamic Content 1.9.1 NULLED

1.9.1​

• Audience Standalone Condition – Added an option to target users who are either inside or outside any audience
• Updated the “Mobile Detect” library (the new version requires PHP 7.4 or higher)
• Bug Fixes

1.9​

• PHP 5.X and lower versions are no longer supported.
• An old format of the DKI shortcodes has been removed. The new version no longer supports the following shortcodes (all of them have new alternatives):
  [ifso_display_user_geo], [ifso_display_user_languages], [ifso_display_referrer]
• The [ifso-redirect] shortcode now defaults to the JS redirect type when rendered within an If-So trigger loaded via AJAX.
• A new filter, “ifso_gutenberg_standalone_widget_forbidden_blocks,” has been introduced to prevent the If-So standalone condition widget from loading on certain Gutenberg blocks.
• Geo-session usage notifications are now calculated based on all licenses installed on the site, rather than separating pro and geolocation licenses.
• The “shortcodes in titles and menus” setting now affects WooCommerce page/category titles and breadcrumbs.
• The “time” DKI shortcode (Also known as the Auto-local Time Disaply shortcode) now supports displaying the current time according to the website’s timezone using the format attribute (optional), for example: [ifsoDKI type=’time’ show=’site-timezone’ format=’n/j/o, G:i’].
• Bug fixes
• Refactoring
• Performance improvments

Changelog didn't updated

= 1.7.1.1 =
* Security update.

= 1.7.1 =
* New functionality - Redirect shortcode improvements: Create a URL template to easily redirect each page on your site to a corresponding page on another domain, subdomain, TLD, or directory. <a href="https://www.if-so.com/help/documentation/redirect-users-based-on-conditions/" target="_blank">Learn more</a>.

1.6.3.1​

• WordPress 6.4 compatibility fixes

1.6.2​

• State targeting now utilizes the Google Maps API for state selection.
• Compatibility with new functions of the If-So Geolocation extension has been enhanced.
• Added the option to “block bots” (can be activated in the settings) (learn more).
• The geolocation request log and analyzer tool now include user-agent data, making it easier to detect and block bots. User agents can be blocked by passing an array of user-agent values to the filter “ifso_block_bots_extra_blocked_user_agents” (User-agent will be blocked if its text contains the value)
• Flag DKI Shortcode: Added a “classname” attribute, allowing users to add classes to the rendered element.
  Ex. [ifsoDKI type=’geo’ show=’flag’ width=’50px’ classname=’class-you-choose’]
• Location override improvements: Added the option to display flags near the country labels in a selection form.
• Location override improvements: Country DKI shortcode is now affected by the override functionality.
• Location override page caching compatibility: The form can now be loaded using Ajax.
• Added the ability to whitelist users from the geolocation “Block bots” mode based on IP, cookie, or by using the geo service in the same way blacklisting is done, but with the “ifso_geo_whitelist” filter instead.
• Allow blocking users from the geolocation service based on the results of custom functions (user role, login status).
• UI improvements.
• Bug fixes.

= 1.6.1.2=
* Added the option to become a geolocation reseller – create sublicenses for clients’ websites and take control of allocating monthly sessions to each sublicense based on their needs.
* Improved the user interface of the geolocation dashboard section.
* Extended access to the audiences page and audience creation/deletion to editors, authors, and other custom roles with post creation permissions.
* Bug fixes.

= 1.6.1.1=
* Geolocation page – Various UI and style changes; added session usage chart to info tab
* Added new filter – “ifso_visit_count_expiration” – letting the user set the expiration of the “returning visitor” cookie
* Enabled if-so conversion shortcodes to work when loaded via ajax
* Bug fixes