Jump to content

Serenade

Member
  • Posts

    273
  • Joined

  • Last visited

About Serenade

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Serenade's Achievements

Senior Member

Senior Member (3/3)

0

Reputation

  1. Another bug likely cause by the implementation of markdown. There is an empty <p> element at the beginning of every staff reply in the ticket system. This is visible in the "viewing email" email preview, and in the customer's actual email as well.
  2. I receive the following error in my console on every page within the WHMCS Admin area: Failed to parse SourceMap: https://www.domain.com/assets/js/lightbox.min.map
  3. If you're looking for something free, check out Serverping's module: http://www.whmcs.com/appstore/962/Stripe-WHMCS-Payment-Gateway.html Just implemented it within our website a month ago and it's worked really well.
  4. Hey cloferba. The versions are 5.3.14, and version 6.2.
  5. Garbage page loads times was a perfect representation of the issue, harsh or not. There's no justification for a 600ms slowdown following a software update. The proverbial here and at this point are specifically referring to the useless back and forth that now populates two pages of this thread, which has since resorted to you accusing me of not being nice enough while reporting an issue which shouldn't have happened to begin with if a shred a quality assurance took place. The "explanations" I received which have now been covered in detail throughout this thread are of no use, nor in my opinion bore any relevancy to the issue. The "suggestions" I received were followed, and did nothing to address the issue. That last ticket, perhaps. However it doesn't inspire a whole lot of confidence said investigation will take place when the subsequent conversations have revolved around "it's your server's fault", "that's cause you're using a custom template" and "that's because of new feature X and Y". Whether I report the issue on a silver platter or not shouldn't matter. Whether you think a 600ms slow down with updated software is a big deal or warrants getting frustrated about does not matter. Two pages into this thread, the fact remains: There is a 600ms slowdown from WHMCS 5 to WHMCS 6 using the same templates on both. The slowdown is not caused by new features in WHMCS 6, since the WHMCS 5 template doesn't use those features. I think everything that could possibly be said besides actually fixing the issue has been said, and we can leave it at that until if and when an update comes out fixing the issue. Since none of the developers have yet to be flagged on the issue, that's unlikely to happen but I suppose you never know.
  6. It's not a sky is falling issue, the only reason the conversation has gotten to this point is direct result of the refusal to investigate the root of the problem, or even bringing the issue up to someone who could do anything about it. I'm not asking how to turn those features off because they are not the cause of the slow down, and I can say this with absolute certainty since I was already informed by your staff switching the WHMCS 5 template would disable said features. As I've mentioned time and time again, the slow down remains using the WHMCS 5 template on v6 and there is no increase in performance doing while running it. The hostility (if that's what you want to call it, I'd call it frustration) hasn't come right of the gate. I submitted a very civilized support ticket two months prior to the one you saw (#BGY-029300) and I was given the same run around and dismissive replies basically saying "that's just the way it is" in v6.
  7. Well then you are mistaken. Two other people in the thread said they noticed the same thing after upgrading. Regardless, I've already explained to you several times why I think more people haven't come forward with the issue. Feel free to check my last few replies in this thread. I love how that's the measuring stick for WHMCS to justify looking into an issue. Unless the sky is falling, who cares right? Here you go again selectively quoting what bolsters your one and only argument that only me and no one else is having this issue. I've mentioned several times over in this thread and the ticket that the issue occurs not only with my custom theme, but also with the default WHMCS 5 template running on WHMCS 6 and the stock templates on both. Also nice little jab there with your "CAP letters throughout" comment trying to paint me as the villain. Only one out of the 11 back and forth replies prior to that has a few words capitalized. Big deal. The reason is was capitalized was to emphasize the fact that 11 replies in, the ticket was still not transferred to Matt despite being told it would be once they had a little more info. Quote: "I apologize it was noted this would be escalated to either Matt or the development team previously as this is not something we're able to do at this time." He doesn't need to visit my site and make it faster. He just has to visit his own to see how poorly WHMCS 6 loads compared to WHMCS 5.
  8. That's because I've made every attempt possible at optimizing load times of every single resource on the site including utilizing Cloudflare's Rocket Loader, minizing and caching. The fact remains however that using the same template on the same server, WHMCS 5.x has an index.php GET request of only 164ms, and that same GET request on WHMCS 6.x averages 709ms. As much as this thread has gone back and forth, there is nothing more to be said. There is something wrong and I cannot fix it as I do not have access the source code, nor do I know what has changed since the v6 implementation. And to be completely honestly, the saddest part this whole situation is the people who would normally be in charge of rectifying the issue are completely unaware because (as you witnessed for yourself in the support ticket) your staff refuses to flag Matt or one of the developers on the issue.
  9. That has no bearing on the issue nor does it justify neglecting the problem. I've already told you why I think more people haven't chimed in, and it's also likely due to the fact this thread was moved (conveniently) to a logged-in only sub-forum which barely sees any traffic at all. Sure: #JLY-852544
  10. Good to know WHMCS values their customers' feedback.
  11. Okay, are you willing to create a module that will verify the email?
  12. Very cool, but if I understand correctly this will not check the email with the MX check right?
  13. Yes, however I want to catch the fake email before the account is ever created. I limit trials to per IP addresses, and I do not want to mess with that. I can't imagine there are that many false positives with the module, and if there are there has to be another module which works better. Facebook has millions of new signups every day and they employ similar mx checks on emails while signing up.
  14. As far as I can tell, all that setting does is requires the user to accept a verification email. I'm looking for something more along the lines of actually verifying if an email exists, similar to what this tool does: http://verify-email.org/
  15. I'm looking for a very basic module that will verify a customer's email on checkout signing up, perhaps using this function: https://github.com/hbattat/verifyEmail
×
×
  • 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