Jump to content

string

Member
  • Posts

    181
  • Joined

  • Last visited

  • Days Won

    8

string last won the day on April 12 2023

string had the most liked content!

1 Follower

About string

Recent Profile Visitors

7402 profile views

string's Achievements

Senior Member

Senior Member (3/3)

41

Reputation

  1. The same here. The WHMCS marketplace, in its current form, exposes vendors to blackmail and reputation damage. After the last incident, we have removed all our products from the marketplace and shifted the business focus away from WHMCS. In the latest instance, it involved an individual using a nulled version of our product along with a nulled WHMCS version. Because their pirated version did not function correctly, they attempted to order a trial with the intention of cracking the new version. For obvious reasons, the order has been rejected. We check every order and require, among other criteria, that the customer does not use a nulled version of WHMCS. Out of frustration for not being able to proceed with their order, the individual left negative reviews. WHMCS, or more precisely, @WHMCS John, shows no willingness to even remotely check reviews, even when presented with crystal-clear evidence of fraudulent activity and the information that it is not expected that the removal of this fake review obligates to check other reviews, where the situation is not so clear. While it is understandable that WHMCS cannot check every reported review, action should be taken when the evidence is so clear. I had long suspected that it was only a matter of time until WHMCS comes up with such a sick idea. I am glad I made the decision a long time ago to no longer participate in the marketplace and realized that the marketplace doesn't really matter at all. The volume of orders has not decreased.
  2. Description Stripe has announced that it will be increasing its payment fees starting April 10th, 2023. However, Stripe is offering a way to minimize transaction costs through its "Link" service (Stripe's one-click checkout). Link is currently advertised as having a transaction fee of 1.2% plus €0.25 per transaction. This gateway allows to accept one-time credit card payments via the Stripe Credit Card checkout. The module supports "Link". Order here (19.99 € / yearly) Screenshot Free Trial For all modules, a free trial is available. Click on the buy link on the top of the site to order. Please carefully note the requirements for a free trial on the page. Compatibility The module works with WHMCS v6.0 and above. PHP 5.6 - 8.1 is supported.
  3. There is no official IDE helper, but there are at least two unofficial helpers: https://github.com/indicio-software/whmcs-ide-helper https://github.com/grizzlyware/salmon-whmcs
  4. Only the online encoder supports PHP 8.1. I think it is safe to assume that WHMCS does not use the online encoder, but the "standalone" encoder product, for which no update has been published yet.
  5. Oh, thanks for tagging me @Danse The module of wsa probably performs a similar task, so similarities in the description are normal, but yes, I also recognize a few "coincidences". The example you brought is awesome 😂. But don't worry, no matter if it's "wordspinned" like you say (the one section is obviously copied 1:1) or not, I'm happy if our modules (and textes) give inspiration. I really don't mind at all. The only reason I'm even going into this is because of this: So this is the first time I've heard that. The module is used well and when there were reports that something was not recognized, it was always due to the customer. There has been an enormous amount of time invested in self-developed tricks to trick the Google / Hotmail image proxy, for example, even with self-hosted domains and so on. First taking over the text (at least partially, see example of @Danse), and then making wild claims - I actually find that a bit cheeky. I would like to have examples with which provider our module doesn't work, but works with yours 🤷‍♂️.
  6. If I don't find something right away, I search for it directly in the database. The SQL queries would be: SELECT * FROM `tbltickets` WHERE `message` LIKE '%123456%' SELECT * FROM `tblticketreplies` WHERE `message` LIKE '%123456%' SELECT * FROM `tblnotes` WHERE `note` LIKE '%123456%' Via phpMyAdmin this also works via the "Search" link in the navigation bar (see attachment). Based on the output, you will find the ID of the ticket / customer. While not as nice as a reasonably integrated search in WHMCS, this works well.
  7. The error message clearly indicates that PHP lacks the permission to create the directory. The most common explanation is that the owner (chown) or permission (chmod) is not correct. I don't think it's the permissions, since the permissions are usually set to 0755 for folders and 0644 for files by default. I'm also unsure why the health check would even attempt to create this directory. Since WHMCS is encrypted, I can't figure that out, but maybe the health check will do that if the configured cron directory does not exist. So I would recommend that you also double check the path you configured.
  8. Looks like a permission issue, probably an incorrect owner of the directories / files. First you should check under which user PHP runs, then check if the owner is correctly set for your WHMCS directory and fix it if not (`chown -R USER:GROUP /path/to/whmcs`).
  9. The problem is that the IDs of the rows in the table start again at 1. To solve the problem you have to adjust the ID of the affected accounts (probably in tblusers) and then you must adjust the AUTO_INCREMENT value of the table so that newly assigned IDs are automatically higher than the previous ones. However, I can't tell you exactly which tables you need to edit. Without insight into the current structure that would be a lot of guessing with multiple eventualities. If you are not familiar with the WHMCS database schema or don't have a good understanding of databases, it probably makes sense to import a working backup or contact an experienced database administrator. Unless you have solved the problem already, I can also imagine that sooner or later even more serious problems will occur. Because if an ID already exists in the database, which would actually be the ID of the next entry, WHMCS will abort in the middle of the action. By "in the middle of an action" I mean for example the creation of a customer account. WHMCS does not really have an error handling for such errors, which will cause even more inconsistencies in the database. But yes, here I am already guessing - it all depends on the exact changes made.
  10. Here you go 🙂 Save this file under /includes/hooks/adminpageSkipSettingsAuth.php (you can change the filename however you want): https://pastebin.com/pRvVzbkn
  11. Yes, that would be the way it should be done. As an alternative you can rebuild the WHMCS module params using this code: https://pastebin.com/SgaBKj2G ModuleBuildParams() should return exactly the same array as you see it in your module functions. But this function is not officially documentated, so I don't know if this function will be changed in a later version, or even exist at all.
  12. If the spam comes from unregistered users, you could enable the "Clients Only" option in each support department: https://docs.whmcs.com/Support_Departments This way, only logged in users will be able to send a contact request. WHMCS will not remove the "Contact Us" link, but when someone clicks on it, they have to log in to create a request.
  13. I see 3 possible solutions: Output the json data at the _ClientArea function Output the json data using a newly created php file Output the json data using a hook Output the json data at the ClientArea function This is the easiest way. An example: https://pastebin.com/vSZ9Aie8 The disadvantage is the SSL checker from WHMCS. WHMCS checks for each _ClientArea function execution if a valid SSL certificate exists (and that can be very slow). However, I believe this check is only executed if the last check showed that no valid SSL certificate exists on the domain. And maybe the behavior has changed in the meantime - anyway, when the SSL checker came out there was this problem and personally I went over using the next option, which should also be somewhat less resource-heavy, because unwanted hooks are not executed. Not that it will make a significant performance difference, but well, if you're running this every few seconds and also possibly by multiple clients at the same time, it's certainly not wrong to pay attention to it as well, or at least be informed about it. Output the json data using a newly created php file You create a new file in your module directory, include the init.php of WHMCS (init.php is in the WHMCS root directory) so you can access all the WHMCS stuff (like the Eloquent ORM) and then call this file via XHR: https://pastebin.com/rYKTYLEk Important: Unlike the ClientArea function, you must ensure that the client has permission to access the service. So if you have a parameter for the service ID, you have to make sure that the user ID (e.g. $_S|E|S|S|I|O|N['uid'] (remove '|' - WHMCS WAF bypass, sorry)) belongs to this service. Otherwise, a customer could view the data of other customers by just changing the ID in the paramters. Personally, I think this is the best approach, because you avoid the mentioned SSL checker problem of WHMCS and it is quite likely that this will also work in future WHMCS versions without any problems. Output the json data using a hook It is also possible that you send output to the client via hook. Here is an example: https://pastebin.com/F9amWiJg I would not go this route if you have access to the source code of the module. It's easy to get the service model: https://pastebin.com/PBBxURX7 Side note Ideally, you create a small HTTP controller to handle the AJAX requests, otherwise it gets confusing if you send many different XHR requests. I'm sorry for posting the code samples on pastebin and to obfuscate some parts. The WHMCS web application firewall blocks my post every time no matter how I modify the examples. I have tried for 15 minutes to get it working. A tech board where you can't post code correctly. Ridiculous, I can't even write SESSION correctly with a dollar sign in front of it. 🤷‍♂️🤦‍♂️
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated