velaware

I started work on a database manager plugin here: http://www.blesta.com/forums/index.php?/topic/1847-database-manager-v001-a/ What's left is pretty simple compared to what I went through yesterday. So, its going to be polished up today. Later on I might make it more advanced (i.e.: delete data from a specific client), which wouldn't be difficult to do. Probably work on that today as a separate feature. Make that a widget. Look for that today as well.

There is the user.login event already but this event isn't fired until after the user is authenticated against MySQL first. The reason for this request is so people can authenticate users outside of MySQL without having to hack core files like I did to do LDAP.

I've worked on this all day today and am pleased to say that I have a version that is showable now. Link: https://github.com/anzenehansen/Blesta-Goodies/tree/master/plugins/database_manager Download: https://github.com/anzenehansen/Blesta-Goodies/raw/master/plugin_databasemanager.tar.gz Its an alpha version as I have limited testing done on it so far. However, from my experience with it, it does well. Features Download backup similar to System Backup Restore backup (*.sql only so far, implementing method to gunzip *.sql.gz files later) Rebuild database (pointless method really but nice for testing to see if it works fine for you) To Do Make excluded table list dynamic (let user pick what tables [besides Blesta essentials] are to be left alone when purging) Decompress gunzip SQL backups Improve rules and validations If anyone else has feedback on this please post. This is my first real plugin for Blesta.Also I will make the logo different. I am not a graphical person.

Sorry for the spam, but fixed the issue somehow. Either it was because I was using "Backup" instead of "backup" in my uses() array or that I didn't call $this->uses() in the backup function. But, it works now.

After studying some of the other plugins more I updated the gist link posted in the original post. I'm now able to render a page and display an error since the Backup model isn't loaded. I'm not sure how to load it, however.

I'm working on my backup management plugin and am running into a snag using $this->Backup->download(). It doesn't send a download and from what I can tell, no errors are generated either. Code of my controller is here: https://gist.github.com/anzenehansen/7d9b2121c1bdde36ae01 Everything renders fine, just when I hit the /backup portion the page loads but then just returns back to the index without anything (the URL even still says /backup in it).

Worst case couldn't you edit the invoice template you use to reflect this?

4.5.2 is the latest but it doesn't support PHP 5.5 (which you have). You have to wait until the creator of ionCube updates the encoder.

I wrote a small Bash script that will help build skeleton plugins (creates the folder structure and initializes some of the files). The URL is https://github.com/anzenehansen/Blesta-Goodies/blob/master/plugin_creator.sh (raw version: https://github.com/anzenehansen/Blesta-Goodies/raw/master/plugin_creator.sh). Just place it in <install dir> (i.e.: if Blesta is installed at /var/www/billing then place it in that folder). You're free to make changes to this script to fit your needs but pull requests are always welcome as I made this in about 15 minutes (including debugging).

Sorry if this is the wrong thread for this. Please move it if not, but I figured it would gain more traction here. I'm writing a plugin right now to mange the database beyond doing just a database dump. So far the feature set of this will be: Restore from said dump (warning included because I get why Paul hasn't done this feature) Table truncation (delete specific tables, just need to get a list of available tables in the database) Custom features for a dump (i.e.: Blesta uses mysqldump to create their database backups, this will allow custom options to be passed) The reasoning for this is because not everyone can or wants to work through the CLI. I.e.: my hosting clients aren't allowed CLI access so they wouldn't be able to restore a database themselves. This will allow them to. What I'm wondering is if there's any more features someone would like to see involved in this. I don't have a real ETA on this but I do plan, once I get the basics down at least, to have it complete within a couple of weeks.

You can extend the API to create the functionality, yes. I'm actually working on a database plugin to do things such as restore from a backup and such right now. I'll add this to the feature set of it. I could see this being viable by default if Blesta included a "Developer enabled" switch or something. But, as a production-ready product like it stands now, not so much.

That'd be my issue then, is that its set to cancelled. Is there a possibility of making it possible to delete the services as well when you delete a package? Also, how can I search the services table by package ID? That info isn't readily available.

Is there a simple way (either via MySQL CLI or through Blesta) to show what services are attached to a package? I'm trying to delete a couple of packages that aren't assigned to any clients and Blesta returns an error saying "The package could not be deleted because a service is currently using it.".

I think for a lot of people, on Blesta or not, it would make the checkout process SO much more easier across the board. I can't wait for this to happen.

I can tell you right now people have suggested the purging of tickets and the devs are strictly against implementing it for a few reasons (quick search of the forum will give you why). What you're explaining doesn't require a feature set, but more so just create a backup of the database at the point you will need to later start fresh from, do your work, then just drop all the tables in the database and reimport your backup. Its really not that hard and you can even use a oneliner to purge them (or add a DROP TABLE case for each table in the backup file): mysql --user=YOUR_USERNAME --password=YOUR_PASSWORD -BNe "show tables" YOUR_DBSCHEMA_NAME | tr '\n' ',' | sed -e 's/,$//' | awk '{print "SET FOREIGN_KEY_CHECKS = 0;DROP TABLE IF EXISTS " $1 ";SET FOREIGN_KEY_CHECKS = 1;"}' | mysql --user=YOUR_USERNAME --password=YOUR_PASSWORD YOUR_DBSCHEMA_NAME

structure.pdt seems to be the file to edit when you want to integrate your site's theme/content into Blesta, so I would go with that first.

This might work but as long as proper PHP error reporting is set up (which typically is by default) it will say something along the lines of "x bytes exhausted maxmium allowed of y bytes". I had this issue before with 2.5.

This is the wrong sub-forum for this. But, anyways, what does your logs in both Blesta and for the web server say? Another thing to check is to make sure your PHP setup has enough memory allocated to it.

I'm just not sure how this would be beneficial personally. I mean, they can simply log in and see if anything. What benefit would this provide to the end user that isn't already built in?

I agree just also want to toss in the other side of the coin as well. The threat is there no doubt but the threat is also not absolute.

First link is kind of one of those paranoia scenarios though. There's a bit of sceince involved that if you want to go to that extreme then you as a sysadmin has more concerns to deal with. As for the NSA one, meh. The RSA algorithm has been implemented by other sources given PKI and the Diffie-Hellman algorithm is public domain essentially. So just because RSA was bought out doesn't mean the RSA algorithm itself is unsafe, you just have to know where the algorithm came from.

I'm kind of confused. How is this different than the emails that get sent out saying "hey, pay for these services for the next term."?

I know this was brought up before but why not let us assign multiple groups to a client? Case in point, I have custom fields set in the "General" group that fit everyone, but also want custom fields set for my hosting clients. Having one without the other hurts a lot.

YAY! Installing this bad boy now

Love the blog article where you guys hinted that 3.1 might be coming out today.