No bug Cancel auto-renewal ++
- Sakis Terz
-
Onderwerp Auteur
- Offline
- Berichten: 50
- Ontvangen bedankjes 0
First of all, I would like to say that I am amazed by the work done regarding the Analytics.
It is really useful and detailed
1. I also like the recurring subscriptions feature and I am planning to use it.
My question is how the user can cancel it, if he/she does not wish to keep it.
2. I have a small wish regarding my API integration.
For the API to work, it needs that node in your extension's xml/manifest file.
<api>
<files folder="api">
<folder>src</folder>
</files>
</api>
I don't know if you need to include any files/folders in your package, though.
The use of that is for the appropriate namespace generation for the files used in api folder for that component.
Cheers,
Sakis
- Ruud van Lent
-
- Offline
- Berichten: 1785
- Ontvangen bedankjes 116
thanks and glad you like the reports, by implementing them as back-end modules you can add them anywhere on your sites administrator interface, not just withing ochSubscriptions.
as for 1.
in the subscription overview the automatic recurring subscribed subscriptions have an extra button, see below: the first one is recurring (ochCaptcha), the second on is where the customer cancelled the automatic renewal (ochResponsiveImages), the customer can then re-enable it or do a manual renewal if he wants.
For 2, I will look into this and add it in the next release: note then when you start utilising this by adding your own api files, these will be overwritten when a new release comes out as that directory is empty or when i start adding files myself.
regards,
Ruud.
- Sakis Terz
-
Onderwerp Auteur
- Offline
- Berichten: 50
- Ontvangen bedankjes 0
I will check if by just adding the <api> node can work, without the <files> and <folders>
- Sakis Terz
-
Onderwerp Auteur
- Offline
- Berichten: 50
- Ontvangen bedankjes 0
Screenshot: www.awesomescreenshot.com/image/58548315...d619712c98250283e988
Can you provide some info on how you did that?
- Ruud van Lent
-
- Offline
- Berichten: 1785
- Ontvangen bedankjes 116
Can you provide some info on how you did that?
Scroll down to "Checkout / Cart indicator"
- Ruud van Lent
-
- Offline
- Berichten: 1785
- Ontvangen bedankjes 116
For 2, I will look into this and add it in the next release: note then when you start utilising this by adding your own api files, these will be overwritten when a new release comes out as that directory is empty or when i start adding files myself.
- Sakis Terz
-
Onderwerp Auteur
- Offline
- Berichten: 50
- Ontvangen bedankjes 0
Thanks for the guidance so far! The issue with the cart counter icon is solved!
I installed the latest version and the <api> node is indeed there.
It turns out that the namespaces are created even by adding that single node in the xml: <api/>
This has the advantage that it does not override any files into the Joomla api folder.
if you go on with the API implementation please consider starting with my code. It a good starting point offering all the necessary scaffolding.
I also have a one small request.
I removed the element with id: "recurring-automatic" in my override but it gives a js error. See screenshot.
Can you please check if that element exists before adding any style there through JS?
Cheers!
Sakis
- Ruud van Lent
-
- Offline
- Berichten: 1785
- Ontvangen bedankjes 116
I also have a one small request.
I removed the element with id: "recurring-automatic" in my override but it gives a js error. See screenshot.
Can you please check if that element exists before adding any style there through JS?
Cheers!
Sakis
- Sakis Terz
-
Onderwerp Auteur
- Offline
- Berichten: 50
- Ontvangen bedankjes 0
Are you going to use the single <api/> node as well?
Also, in the future I would like to present different products in different groups.
E.g. Products and Services or Single Products and Bundles
See: breakdesigns.net/pricing/
Is there any plan to use the Joomla Categories or Tags for the OCH Subs Products?
- Ruud van Lent
-
- Offline
- Berichten: 1785
- Ontvangen bedankjes 116
Great!
Are you going to use the single <api/> node as well?
So there is only an issue when you have a file and I also have that file (with different content).
so using single <api /? node doesn't make a difference.
I thought about that, but merely for the product overview so you can then 'filter by tag or category'.Also, in the future I would like to present different products in different groups.
E.g. Products and Services or Single Products and Bundles
See: breakdesigns.net/pricing/
Is there any plan to use the Joomla Categories or Tags for the OCH Subs Products?
That is the only use case I see as you can now already have products with multiple files in them: like my agency bundle.
So If I was to make a social media 'category', I could just make that a product that would then give access to ochSocials and ochOpenGraph: no need for a category.
So no, there is no plan