Attached a new version of the package.
I've made improvements after feedback from the Woltlab team.
Ok, since Woltlab takes more then a week to validate my package, I will share it here.
Enjoy and please don't hesitate to contact me in case you have any question or suggestion!
-Edit: added new version of the package in the post below.
Ok, I made some improvements in the code and submitted it to Woltlab.
Let's hope they will approve it.
If they do, it will become available at following URL:
Still waiting for feedback from Josh.
But if you want, I can share the package already?
Ok, after long long waiting time, the payment system is now available in English and I can launch my package.
Beta testing can commence.
Update: I sent the code to Josh, so he can have a first look at it and prevent major mistakes before going live.
I am selling in the shop a ticket for an event.
When users however want to buy a second ticket, they cannot.
The text is replaced with 'bought'.
Is there a way to allow users to buy the same item multiple times?
2 More steps need to be finished:
- the payment provider is translating everything into English. He is finalizing the last pages.
- I then need to update the package to allow you to choose the default language in the acp
Sorry for the delay. I'll keep on pushing as much as possible.
I received a German translation.
I'm now waiting for the payment provider to have the system available in English.
He is planning on finishing it this week.
After that, I will implement the multi-language support inside the package and share it with you.
I can try to add that later on.
For now it will be a simple payment system.
- every payment method and amount can now be defined in the acp controlpanel
- Tested compatibility with jCoins 1.1.0
- Made the name jCoins change depending on the name selected in the configuration of the jCoins package
- Make certain everything is translated and available in English
- Translate the package also to German afterwards (see below)
If anyone has time to translate the attached file to German, it will help a lot.
Thank you in advance.
Indeed, that's how I did it in the end.
I managed to crash my webserver by using a wrong setting in the richest user dashboard box...
You have an option to set how many users should appear in this dashboard box.
I put it on 0, as I do not want hackers to know how much money everyone has.
This resulted in the dashboard box listing all users I have in my database and consuming all the memory => crashed nginx.
If I'm stupid enough to input 0 (thinking I could hide the box that way), others might be doing this mistake as well.
Not a critical bug (minor), but just to have it listed in this thread.
Great, thank you!
If you disable the option in the usergroup that users can see Jcoins,
it hides the JCoins properly inside the threads, but the JCoins are still visible inside the profile pages.
I do not want users to see the amount of Jcoins from other users.
Is this the profile page?
If so, it's missing the IF statement.
Ich habe ein pakket geschreven mit dem man JCoins kaufen kann.
I've written a free package that allows users to buy JCoins.
Payment methods supported:
- Bancontact / Mistercash
- Bankwire (manual bank transfer)
- Phone call payments
- SMS payments
If you would like to beta test it, please don't hesitate to send me a private message.
On the page https://tims.bastelstu.be/index.php/JCoinsTransfer/ it would be good if the username would use the WCF autocomplete functionality.
That way you are certain you are sending the Jcoins to the correct user.
Auf der Seite https://tims.bastelstu.be/index.php/JCoinsTransfer/ wäre es gut, wenn die WCF Benutzername-Autocomplete-Funktionalität nutzen würde.
So sind Sie sicher, Sie senden die Jcoins dem richtigen Benutzer zu.
I quickly wrote some code for this and did a pull request on github:
It's the first time I do it this way, all feedback is welcome.
I hope you will add this feature.
It would be nice if we could also give users JCoins after posting a new blog post (using woltlab's blog system).