Jump to content

EidolonHost

Members
  • Posts

    281
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by EidolonHost

  1. Alright, finally starting to get back into developing the module.

     

    It will take me a bit to start cranking out a fix for all the current issues that I've notated in the OP and made sure the module's properly set up. I need to refamiliarize myself with the module again since it has been a while since I last worked on it.

     

    Of course, as always, comments, code-fixes and suggestions are always highly welcomed.

  2. If Blesta showed 3.5.1 in the footer, then you couldn't upgrade to v3.6.0 because the system was using files from version 3.5.1. In other words, Blesta thinks you're upgrading from v3.5.1 to v3.5.1 (i.e. no upgrade necessary). This only occurs if /app/app_controller.php was not overwritten with the one for v3.6.0. Once it is uploaded, the version shown in the footer of the admin UI will appear as version 3.6.0. At this point, running the upgrade at ~/admin/upgrade/ will upgrade the database to the latest version.

     

    Everything's resolved but I just wanted to say thanks for clarifying why this was happening. Now that I know this, I'll be making sure I do the appropriate rituals next time upgrade time rolls around for both my development and production environment. :P

     

    So, TL;DR: Forcibly overwrite /app/app_controller.php if you can, otherwise, save blesta.php in config/ outside of where the billing system and download the new copy of the software, put blesta.php back where it belongs. Along with relevant modules and do ~/admin/upgrade.

     

    Should help someone else next time someone else runs face-first into this and tries a search. :) (and future me, as well)

  3. Haha I need sleep sorry that's what I meant.

     

    Ah, gotcha. Yeah, I saved it. :)

     

    Thanks for your help. I've resolved all but the license manager issue... that should've been Captain Obvious to me... although.. I am still curious as to why the system didn't properly upgrade until I basically did the nuke from orbit option... eh. So long as it works, it works, right?

  4. Download manager > paid extensions or contact the support team to find out why you don't have permission.

     

    Hope you did save the config.php

     

    ... Uhhhhhh, I don't think I did. Just the blesta.php. Why? <_<

     

    Edit: Looks like I gotta raise a tix to 'em about not having access to that.

  5. You sure the files aren't in the /blesta folder still? Or cPanel is doing what it has done to a customer of mine and refused to override files so he had to use FTP.

     

    Mine's VestaCP. I had to forcibly rm -rf and unzip the new copy of Blesta 3.6.0 since FTP was for some reason refusing my connection as well. SSH was the only thing that worked. Not even SFTP. :P

     

    But it seems to be all good, aside from that error at the end of the upgrade process.

     

    Edit: Looks like I spoke too soon. Checking the modules and hitting the Blesta License Module upgrade button results in the License Manager throwing an error, as seen above in the earlier post.

     

    Edit2: Oh wait, I derped. I'll have these fixed shortly. :P

     

    Edit3: The errors I had are fixed... but the one above, I'll need to grab the License Manager module... and I don't seem to have access to that in my account with Blesta.

     

    Edit4: Had to remove active packages. Tried uninstalling the module then installing it. It's now no longer present in the system. So uhh... yeah.

  6. Attempting to upgrade will redirect you back to the dashboard if the upgrade has already been performed. Similarly, if it completes successfully, you will be redirected back with a message that indicates it was successful. Are you sure the upgrade is not already completed? Are you sure all files have been uploaded?

     

    Look at the database and check the `settings` table for the setting with `key` = database_version. What is the value? A value of '3.6.0-b1' is the latest version.

    Also look in the footer of the admin UI to make sure the version is 3.6.0.

     

    Footer says 3.5.1. I mentioned that in the OP, rather, I said I'm on 3.5.1, which is the same thing. Checking database now.

     

    I did get the immediate redirect to the dashboard but no successful message regarding the upgrade. Database version says 3.5.1, as well.

     

    Edit: Also, I made sure to overwrite all the files when I unzipped the zip directly on the server. No change at all. It's really odd.

     

    Edit2: I decided for the nuke from orbit option since it wasn't wanting to work properly.

     

    Here's what I did:

     

    rm -rf everything in the billing area after copying blesta.php to a safe place so it doesn't get nuked. Redownload 3.6.0. Unzip everything. Use hotfix to enable it to work on the latest version of php... then finally, copy blesta.php back to the config folder.

     

    Hitting admin/upgrade did the trick... but I shouldn't have had to do that. Database now reports that it's at 3.6.0-b1

     

    Edit3: Sidenote, this occurred after I hit admin/upgrade:

     

    Oh noes!

    Module 'BlestaLicense' does not exist. on line 29 in /home/eidolon/web/eidolonhost.com/public_html/billing/components/modules/modules.php 

    Printing Stack Trace:

    #0 /home/eidolon/web/eidolonhost.com/public_html/billing/app/models/module_manager.php(910): Modules::create('blesta_license')

    #1 /home/eidolon/web/eidolonhost.com/public_html/billing/app/models/module_manager.php(356): ModuleManager->loadModule('blesta_license')

    #2 /home/eidolon/web/eidolonhost.com/public_html/billing/components/upgrades/upgrades.php(316): ModuleManager->upgrade('4')

    #3 /home/eidolon/web/eidolonhost.com/public_html/billing/components/upgrades/upgrades.php(85): Upgrades->processExtension('module', NULL)

    #4 /home/eidolon/web/eidolonhost.com/public_html/billing/app/controllers/admin_upgrade.php(102): Upgrades->start('3.5.1', '3.6.0')

    #5 /home/eidolon/web/eidolonhost.com/public_html/billing/lib/dispatcher.php(111): AdminUpgrade->process()

    #6 /home/eidolon/web/eidolonhost.com/public_html/billing/index.php(21): Dispatcher::dispatch('/billing/admin/...')

    #7 {main}

  7. So... obviously with the release of 3.6.0 out...

     

    First thing I did was try to upgrade. Unfortunately... it pretty much hilariously failed. As in... every time I tried to do /admin/upgrade it simply redirected me to the dashboard.

     

    I'm on 3.5.1, but I'm having trouble trying to get the system to upgrade to 3.6.0. Is the upgrader missing?

     

    I'm looking through stuff and I can't seem to force an upgrade at all. It's driving me nuts.

  8. Alright, so.

     

    I created this thread so that we can all discuss things we need to talk about in the Tasty InterWorx module by ModulesBakery now that it's been released as Open-Source on Blesta's Github here.

     

    I've already done some preliminary testing and while the module does work, it has some issues that needs to be resolved. We can discuss about those here and how we'd resolve them here, so as not to clutter up the ModulesBakery closing thread.

     

    We should talk about documentation for the module here, as well, I think.

  9. Tasty cPanel

    https://github.com/blesta/module-tastycpanel

     

    Tasty Interworx

    https://github.com/blesta/module-tastyinterworx

     

    Digital Ocean

    https://github.com/blesta/module-digitalocean

     

    All released as FOSS (free open source software) under the MIT license.

    Very nice! Also, grabbed the modules to test them out. Note: Your modules need to be renamed exactly as the php files in each are described.

    ie, if you plan on using the digital ocean module, you will need to do a mv operation on the file. By default, that's module-digitalocean-master if you wget the master.zip from Github. You'll want to rename it to digitaloceanmodule if you want it to show up in the Available listing under Modules.

  10. Script in OP is now updated to work properly, for the most part.

     

    The only remaining issue now is that you still get an e-mail regarding the failure of the md5sums. But if you go to actually check the md5sums for the GeoLite2-City database, you find they're the exact same.

     

    I'm not sure why this is, just yet... but by and large, you should be able to just throw this into a script, set it up in cron to fire when MaxMind updates their stuff each month.

  11. Hello everyone,

    I am so sorry for the bad news,

    Some people said that since they're not developers having the source code isn't useful for them. The original plan is to provide the source code to the license holders only so they can at least be able to improve them as they need, however, if there are many requests for open sourcing them so other developers can support it and improve it further, well, i have no problem with that.

     

    I think you should open-source everything you have, except those that have had clients insist on you transferring the rights to the code to them.

     

    That way developers and even yourself can continue working on the developed plugins and modules. Why let all of your work go to waste? Those that need the modules will use them and those that can work on the modules to keep them updated, can and will do so.

     

    There's no real reason to not open-source everything all at once.

  12. Very bad news about modules bakery closing, now what we suppose to do. We  can continue using the tasty cPanel  module but what will happen if cPanel  or blesta make a big upgrade and the module need to be update too. Is very sad to hear that they are closing but hopefully  someone else will take they work and continue offering that solution because it works great.

     

    * Any one knows about other solution for cPanel  module for blesta that we can use as a backup?

     

    I think they will be open-sourced. The e-mail states that anyone that purchased any of their modules will be given the source-code free of charge.

  13. Hi everyone, today I received an email with some unfortunate news that ModulesBakery is going to close their business by the end of October. I don't know what this will mean for me and other customers. They are saying that they will send us the source code for the module we purchased but I am not a developer so there isn't much I can do with it.

    I must admit I was skeptical about buying Cpanel Extended and look what happened to them, then ModulesBakery came alone with Tasty Cpanel module and it looked promising and so this time I decided to make the investment. And I am calling it an investment because it's not just the money spent but also the time to change settings and edit email templates and test and so on. I feel like the best way forward would be for me to return to the stock Blesta Cpanel module but I am not even sure whether simply back tracking my steps would work or result in catastrophic failure.

    I would like to know your opinions, expecially from others who are affected I would like to know what you intend to do.

    Thank you

     

    First thought, "NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO"

     

    Second thought, "Dammit, I enjoyed working with them even if we hadn't gotten anything started with them... what the hell happened?!?!"

  14. Yeah, that's the gray area, and I'm not a lawyer, but my interpretation is that if it is completely optional and not enabled by default (e.g. the download does not happen automatically unless and until someone checks a box), then it should be ok.

     

    Ahhh, I gotcha now. Herp. Yeah, I believe you're right on this. Hopefully that's all it'll take.

  15. I think that's sort of a gray area, in terms of licensing. We can't distribute MaxMind DB with Blesta, and some users use a shared MaxMind DB. But we'll evaluate when we get there. If nothing else, a plugin could be created to auto update MaxMind DB.

     

    I don't think that'll be an issue. I meant having the ability to have Blesta download the DB for you on an automated basis. As you said, you just can't distribute the DB with Blesta but you can set it up so that it'll download it for you on an automated basis.

  16. At first there was a glaring issue in that Start Menu wasn't working... up until I connected to the Internet, anyway.

     

    Seems to be okay now. No issues here... yet, at any rate. Except for SorensonVRS's nTouch PC app constantly restarting for some reason.

     

    Edit: Oh, and not being able to fully shut down. Someone on Reddit had the solution for the issue. Turns out that by default, Windows 10 does fast restart, instead of a full shut-down.

     

    Power Options > Choose what closing the lid does. Click on the blue Change settings that are currently unavailable. Untick fast restart, save. Shut down as normal, force a hard reset then log back in, shut down again and it should work as you would expect.

  17. Script does not work -- did you try it out in your shell? By default curl streams the data to standard output. You are not capturing the output. Every line after that is incorrect. Your logic on checking for MD5 is backwords -- if you ask me. Read the man page for the command md5sum (man md5sum).

    Yes, that goes in your crontab file (/var/spool/cron/) Do not forget the &&. The following does everything you need:

     

    0 9 * * 3 [ `date +\%d` -le 7 ] && curl -L https://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz | gunzip > /srv/uploads/system/GeoLiteCity.dat
    
    No, the script is not good. Please test before posting. Depending on what philosophy you subscribe too, I am of the idea that I should only be email when something bad happens. Since you plan on making this into a cronjob, cron can email you the output of a script. So only print to standard output (or error) in your bash script when it fails. Get ride of the verbose printing would be what I suggest.

    -Adam

     

     

    Ack. Sorry about that, I'll need to shellcheck more carefully.

     

    Edit: OK, I think I've got it... it works for me now that I've corrected the issues. Can I have someone else test and confirm? It should work now. I'm not the greatest at bash scripting. :c

     

    Edit2: Er... looks like it works fine but not quite in the way I intended. I just got an e-mail from the server about the md5sum results... it was supposed to e-mail me on failure of the md5sum test. Looks like I need to fine-tune it a bit more.

     

    Edit3: This is a bit frustrating, trying to fine-tune the script to e-mail on md5sum error failure.

×
×
  • Create New...