Paul

I don't oppose either of these, and both are fairly popular. Anyone else use them?

No, it has nothing to do with licensing. It's just a common way to do caching. There's no need to make slower API calls for every page load when the data isn't changed frequently. This is more similar to what w3tc does for Wordpress.

I would cache it to disk. serialized array written to a file, read the data from the file instead.. then, randomly on page load make another API call and overwrite the file. 1% of page loads should be enough.

I think that's a good answer

I actually experienced a bug related to this yesterday because I have a cPanel license with buycpanel.com. They normally charge my credit card every month, but I strangely got a late notice. So, I login (to whmcs) and click the card on file, enter the CVV and go to pay, and it says there is an error. So I contacted them and asked if it was related to the whmcs patch, and they responded with..

Is it Aug 14th yet?

Here are a few.. CORE-604: Merge tickets CORE-605: Custom ticket statuses CORE-606: Staff signatures CORE-607: Split tickets Some of the others need more planning before I can assign a task to them, including the automatic actions, which we want to implement but it's pretty involved, at least how we want it to work.

Is it because of a KB you asked them for a quote on?

http://www.blesta.com/forums/showthread.php?t=1974 ModulesGarden wants some feedback on what modules they should build for Blesta v3. Please vote on this thread on the other forums. Thanks!

It may be MariaDB, do you happen to have a MySQL server available? dump the database and import it and update the config/blesta.php database details? That would be the most sure way to determine if it's contributing to the issue And if it is, I wonder if there is something we can do to fix it in MariaDB as well.

They are on their 4th build for the same patch now?

You don't have to worry about that, any change automatically calls for a new version number and release. What they are trying to do is avoid the embarrassment of patching a patch. We're a little less amateurish.

I suggest upgrading ASAP, some broken stuff is better than a compromise. With a patch out, all an attacker has to do is run diff on the files to see what they changed and they will know the attack vector.

What is that?

It is getting pretty ridiculous. Someone commented on Facebook..

Fortunately, we kinda sorta know what we are doing. If you are hoping we go mad and screw you over, don't hold your breath.

I'm not sure plugins have the ability to render different pages depending on the client group, at least there is an issue with the navigation link as those are preloaded and cached. I need this ability too, so we will definitely be looking into it. We do custom development, but we are not taking on any projects until after we release v3.

The problem is coming up with a few free days to do it, we are pretty slammed to make the deadline as it is.

It's suppose to, but I'm not sure it does.. at one point it definitely didn't but I think that was fixed. Better yet, do a fresh install.. re-issue for it, and then re-issue again when you're done and back to your primary install.

What do you mean? I think they are doing a great job!

That's reassuring, lol. I need a bigger house

What I would do is uninstall the support plugin, and reinstall it and see if it still behaves the same way. It's possible it's a side effect of some change along the way that wasn't properly addressed in an upgrade. Also, I'm not sure how many people are using MariaDB. While it's suppose to be a better performing clone of MySQL, there may be a compatibility issue with the particular query that is used to fetch this information. If it's possible to try it with MySQL, or get feedback from someone else who happens to be using MariaDB I think we could advance this closer to determining the cause.

Very cool! I could get use to seeing Blesta shirts, that's for sure.

What are the pages for?

Does your support plugin need to be updated? Check Settings > Company > Plugins > Support Manager and see if there is an "Upgrade" button there. If so click it. I don't recall this ever being a bug, so that may not accomplish anything, and I'm unable to duplicate this. Anyone else having this issue?