Jump to content

velaware

Alpha Developers
  • Posts

    346
  • Joined

  • Last visited

  • Days Won

    8

Posts posted by velaware

  1. 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.

  2. 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.

  3. 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).

  4. Thanks for your reply. But test.php says version 4.5.2 is installed which is the latest version?

    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.

  5. 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).

  6. 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.

  7. I think that having these scripts for testing makes perfect sense personally.  I would not want that functionally to be available in my production code as I would not want any of my data deleted if I can help it.  This is where one off scripts help solve these problems.

     

    On the same note can't you extend the api via a module to add those features in for yourself if you need them?

    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.

  8. In that case, you could use Blesta's search feature to search for the package by name, and that should return you a list of services that use them.

     

    The services attached to the package would need to be deleted first, and Blesta does not provide a way to delete a service (due to data integrity), unless the service is pending/in review. If a service exists of a different status (active, canceled, etc.), then you would have to physically remove the service from the database.

    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.

  9. Hi Dev Team,

     

    We have been testing Blesta and the API integration with our systems, which often requires a reset and clearing out of customer data so we can re-use the same email addresses and customer details from scratch.

     

    Can we please add to the feature list a function in the admin section to 'Clear Customer Data'.

     

    The goal would be to remove all customer data, including history of tickets and invoices, resetting the database back to a clean setup with all the system wide configurable options - but not the customer data.

     

    Cheers,

     

    D.

    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

  10. Hello,

     

    We would like to add our floating live help button to all pages on the 'client side' which is usually done in a 'footer' file.  We aren't sure what file to edit to do this, can someone point us in the right direction?

     

    Thanks,

    Larry

    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.

  11. Can you replace the blesta files except the config file.

    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.

  12. I want to send a full services list each month, as a reminder of all the services and renewal they have.

     

    The emails about "hey, pay for these services for the next term" only sends out the list of services that will expires in the current month ?

    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?

  13. Please consider

     

    http://phys.org/news/2013-12-trio-rsa-encryption-keys-noise.html - "Research trio crack RSA encryption keys by listening to computer noise"

     

    http://www.forbes.com/sites/timworstall/2013/12/21/researchers-break-rsa-4096-encryption-with-just-a-microphone-and-a-couple-of-emails/  - "NSA paid RSA $10 million to adopt an algorithm that wasn’t entirely secure"

    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.

×
×
  • Create New...