laterpay / laterpay-typo3-extension Goto Github PK

The debugger renders without styling, if you look at the frontend of a TYPO3 installation with the debugger on.

As an admin,
I should see a debugger pane in test mode (see #12) that renders all relevant environment variables, plugin configuration, and information regarding code flow,
so I can analyze bugs and integration problems.

As an admin,
I should be able to create time passes, that grant access to the entire site or one selected category for a selected duration at a selected price (either as Pay-per-Use or Single Sale purchase),
so I can sell multiple pieces of content as a bundle for a limited amount of time (similar to a subscription, but without automatic renewal).

As I understood @mturalenka, for some strings (e.g. in the teaser overlay), the respective labels for translations have to be added to the locallang file.

As a user,
I should see a preview version of the content plus a purchase button before I have purchased a piece of paid content and only get full access to the content after I have completed the purchase,
so I can get an impression of the premium content before purchase.

The preview content should be defined manually in an additional “teaser content” field that is integrated with the add / edit content page.

The customer just reported, that the teaser (the text from the teaser text input, not the text under the overlay) is shortened: Only 10% of what's defined as teaser is actually displayed, followed by "...".
It seems, that for the teaser, the same length rules are applied as for the text under the overlay.
The correct behaviour would be, that the teaser is displayed in it's full length and only the text under the overlay follows the rules definded in the "Appearance" section.

@mturalenka Could you please have a look and assign accordingly?

As an admin,
I should be able to set individual prices for each piece of content in the Pay-per-Use and Single Sale revenue model,
so I have full flexibility in pricing my content.

Fatal error: Can't use function return value in write context in /var/www/typo3/typo3conf/ext/laterpay/lib/hook/class.tx_field_checker.php on line 66

Remove unused functions (classes).

They are ugly and unnecessary.
(e.g this one <h3 class="uppercase">Account:</h3>)

The extension should offer a caching compatible mode that recognizes popular caching solutions that cache data or entire HTML pages and can be manually switched into caching compatible mode from its settings page.
In caching compatible mode it should render only the preview content of paid content and check via Ajax, if a user has bought that piece of content and render that to the user.

Replace dummy functions such as get_option(), update_option(), etc. by correctly named class methods

The extension should automatically generate teaser content for paid content that does not have any teaser content defined by extracting a defined amount from the full content.
The automatic extraction should be defined by three parameters:

• percentage of content -> percentage of content to be extracted (values: 1-100); 20 means "extract 20% of the total number of words of the post"
• minimum word count -> MINimum number of words; applied if number of words as percentage of the total number of words is less than this value
• maximum word count -> MAXimum number of words; applied if number of words as percentage of the total number of words is greater than this value

We should generate a new set of Sandbox credentials for a merchant called 'LaterPay-TYPO3Demo' that can be distributed with the TYPO3 extension.

On the flipside of a time pass, there is no unit displayed for the validity period. For 1 day, it just displays "1".

@mturalenka Please feel free to assign that ticket.

Everything else unchanged, users with role "editor" should be able to

• make content paid content (i.e. set a price for it) and
• preview paid content as it appears for visitors or admins

TYPO3 coding standards should be enforced using PHPCS with the official TYPO3 ruleset:
https://github.com/typo3-ci/TYPO3CMS

When I try to set a price of 6.00 with the revenue model SIS, I get the following error notice:

102: These fields are not properly updated in database: (laterpay_price) Probably value mismatch with fieldtype.

The extension should have an authorization concept that grants specific viewing and editing rights to users based on their user role.

The extension should support the standard TYPO3 update and release process, so updates can be distributed in a standard way.

most of the methods descriptions are wrong or not informative

As a user, admin, or crawler,
I should be able to view (RSS) feeds of the site, but only see an excerpt of the full content for paid content,
so I can stay updated on new content.

currently a lot of places where code is not aligned well, spaces amount are wrong etc
additional task:

• update phpcs rules to check these issues

Our customer said, that it would be good, if the default value in the price input for new content is 0.25 – They would prefer it to be 0.00, as most of the new content they create is free. So we should change the default value to 0.00

@mturalenka Could you please have a look and assign the ticket?

As an admin,
I should be able to view detailed statistics about page views, conversion rates, sales, and revenue,
so I can analyze the performance of my paid content.

The extension should track unique visitors and log all details about page views and purchases in a database table.

The teaser overlay covers both the teaser content and fulltext.

@mturalenka feel free to assign that ticket.

to avoid issues with folders permissions to create cache file we need to distribute it by default with extension

JSHint should be used with a LaterPay standard configuration to lint all Javascript code.

The extension should detect user agents that can not handle forwarding and serve them the preview version of the content instead of running them through the LaterPay token assignment process,
so they won't report errors for search engines, social media platforms etc.

Use browscap to test for user agent capabilities.

The purchase dialog doesn't show a title – from my point of view, it should display the title of the respective page.

@mturalenka Please feel free to assign the ticket.

I found that TYPO3 injects a lot of paragraphs into our views that break the appearance.

For example in wrap.html inside of <div class="lp_benefits"> and <div class="lp_poweredBy">.

As an admin,
I should be able to switch between the live mode and a test mode that works against the LaterPay sandbox and where the extension is not visible to visitors of the site,
so I can test the plugin and tweak its configuration without a staging system.

As an admin,
I should be able to manage relevant settings from the TYPO3 backend, such as time passes configuration, extension mode, and API credentials,
so I can configure the extension according to my needs.

I compiled a list of UI elements, which should be removed from the current Typo3 plugin backend as those features are not available in the plugin currently. @yastapenko-ScnSoft please have a look at the list and check, if the functionality is indeed not available in the current Typo3 plugin before removing the according UI elements.

Pricing Tab:

• Toggle for "time passes only mode":
  
• Global Default Price:
  
• URL input for gift cards:
  
• Bulk Price Editor:
  

Appearance Tab:

• Gift Card Section:
  
• Content Rating:
  
• Premium Shortcode Section:
  
• Integration into Theme section:
  

Dashboard:

@yastapenko-ScnSoft I'm not sure, which part of the dashboard is actually working / supposed to work. Could you provide further information about that, please?

A merchant says that his social media plugin (it shows a social media bar below each article) is not working anymore, the bar is not displayed. There now is a Javascript error

"$(...).socialSharePrivacy is not a function".

Their admin said it might be because of the LaterPay plugin.
@mturalenka Could you please assign that ticket? It would be good to have that solved soonish.

A customer reports, that the teaser content is replaced by an automatically generated teaser when saving the content for the first time. After changing the teaser again, the individual teaser is saved as expected.

@mturalenka Could you please assign this ticket?

That table can grow quite large. We should prevent it from becoming too large.
One option would be to truncate all records that are older than 3 month, because those won´t be analysed by our statistics feature anyway.
laterpay/laterpay-wordpress-plugin#16

For testing purposes, we should set up TYPO3 on two DigitalOcean servers.
As they don't offer a TYPO3 image, I would spin up the server with a Linux distribution of your choice, you install TYPO3 and everything, and I then store that as an image for additional servers.

according to the fixes made in wordpress plugin need to update typo3 plugin:
laterpay/laterpay-wordpress-plugin#731