1.2.4 - Main update

This version adds a configuration option where you can specifically define that the Paywall should be rendered client-side.

This option prevents issues with expired JWT tokens when loading Paywalls from cached pages, which might occur if pages are cached more than 5 minutes and the JWT token has expired.

This is main release which builds upon version 1.2.3.4.

1.2.3.4 - Minor update release // Corrects previous beta

Corrects previous release 1.2.3.4-beta.

1.2.3.3 - Paywall client-side rendering

This update adds a configuration option where you can specifically define that the Paywall should be rendered client-side.

Actually, the Paywall is already rendered client-side, but this change also makes sure that the JWT signature needed for the Paywall is rendered on every visit, even though the page might be cached.

This change prevents issues with expired JWT tokens, which might occur if pages are cached more than 5 minutes.

This update builds upon the main 1.2.3 update.

1.2.3 - Main update

This version adds the following features:

Logged in as a permission
In addition to setting a subscription as a requirement for a content object, it is now also possible to define that content should be readable for logged in users without a subscription.

Session identification
It is now possible to skip session identification for content that is not restricted, this option is available as a switch on Payway settings panel named "Only establish SSO session when visitor views restricted content".

1.2.3.4 - Minor update release

Based on 1.2.3.3, adds 2 new methods for fetching the "Payway Portal Base Url":

• Tulo_Payway_Server_Public::get_myaccount_url()
• Tulo_Payway_Server_Public::get_portal_base_url() - alias for get_myaccount_url()

Not a mandatory update, will be merged into main in the next release.

1.2.3.2 Logged in as a permission - beta

Update fixes actual check for logged in user.

From 1.2.3.1:
With this beta release it is possible to add a restriction to an article/post that only requires the user to be logged in to be able to view the article/post content.

1.2.2.3 - Session identification option - beta

This update adds a new config option for SSO, making it possible to select if an SSO session only should be identified when visitor accesses restricted content.

Leaving the setting "SSO session for restricted content only?" to off, which is the standard behavior, every visitor to the website (except crawlers and bots) will be identified with a SSO session. Setting this setting to "on" will only identify an SSO session if the visitor accesses restricted content.

1.2.3.1 Logged in as a permission - beta

With this beta release it is possible to add a restriction to an article/post that only requires the user to be logged in to be able to view the article/post content.

1.2.2.2 Paywall checkout

Sometimes Wordpress throws you a curveball, this is a bugfix release for 1.2.2 fixing generating the "Ticket Login Url" needed for Klarna checkout paywalls.

From 1.2.2
This release brings the Paywall functionality in the plugin up to par with the actual production release of Tulo Paywall with Klarna checkout.

The last missing piece in functionality this version adds is autologin of the user after a completed purchase, which makes it possible for the user to click "Read article" in the confirmation dialog and read the article directly as a logged in user.

1.2.2.1 - Paywall checkout

This release is only a version bump, no other changes since 1.2.2

From 1.2.2
This release brings the Paywall functionality in the plugin up to par with the actual production release of Tulo Paywall with Klarna checkout.

The last missing piece in functionality this version adds is autologin of the user after a completed purchase, which makes it possible for the user to click "Read article" in the confirmation dialog and read the article directly as a logged in user.