MarkTheDaemon
-
Posts
25 -
Joined
-
Last visited
-
Days Won
1
Posts posted by MarkTheDaemon
-
-
Then they do a "The Works" and "The Entertainer" shops in the UK, they hire someone to work on their website side to do all that. The Works has one guy who adds all their products to their website, takes pictures, writes descriptions. If they can do it, so can others.
If you say so. I just know there are thousands of small businesses out there in the UK alone that look at billing solutions like Blesta, and not every one of them can afford to outsource to pay someone to do it for them.
I've made the suggestion but I get the impression it's not being well received so I'll leave it at that.
-
If they can't do little code edits, personally I believe they shouldn't bother in the internet market where we live on basic <a href=""></a> <b></b> <u></u> <br /> I Learned that back when I was 13. Way before I was working for a webhost and before I owned my own. And even a basic person can copy and paste, unless they can't use a computer.
If you was using WHM** / Hostb*** / ClientE*** you couldn't get it so easy you could didn't have to touch a bit of code.
But Blesta is a billing system, and you can use it for so much more than just the "internet market". What about an architect, or writer working freelance? They aren't anywhere near the web industry but could still use Blesta quite happily for their invoicing and administration. I wouldn't expect them to know the first thing about editing code. At the end of the day they are paying for the product.
Maybe I'm out on my own on this but I see a lot of potential for different markets outside your usual "web host billing".
-
But if your going to be like, I don't want to do anything, has to be automatic. If your that lazy, time to close shop.
Great attitude.
I look at it from the point of an end user to try improve the software. Some end users will be technically competent enough to make changes here and there to get the set up working just for them which is fine. Other users just want the software to work and don't have the ability or interest in making code changes all the time to make something as basic as this work correctly.
This isn't an issue for me, I'll just remove the code, but I assumed that the developers here would want suggestions and feedback on how to improve the product for everyone. This includes companies that bill clients but perhaps not in the technical/web industry. Massive market. Don't just automatically assume that everyone that uses Blesta is competent in HTML/PHP.
Just my opinion, for what it's worth.
-
Why not have a WYSIWYG style thing for everything from pages, to modules, that way you don't have to move a finger?
Because you are expecting end users to have a grasp on editing HTML/PHP files. Don't set the bar high, not everyone that uses Blesta will be a web host, it's a billing system that a lot of companies can use that aren't technically competent in programming.
-
The ability to add custom links to the client navigation bar without diving into the code would be a good addition. For example, if you have a support system (Kayako et. al) that you need to link to, or a forum etc.
-
-
Yeah I know, I've done that but we shouldn't be making end users remove bits of code if they don't want to keep the portal plugin.
-
Not sure if this is a bug because you can remove it or add it in, or rename it to billing home. I'm not sure if we have a if statement for if on a page show this else show that.
Where is the setting to remove/add/rename it? I've removed the Portal plugin and the link is still there which doesn't really make any sense to me.
-
-
The "Return to portal" link should not be visible when the Portal plugin is disabled, it may add confusion to the end user.
Cheers,
Mark
-
Removed the system key generation code and the file was written successfully with database details and the dummy details I used for $system_key.
However, once on the initial setup page after filling in my details it just returns a blank screen. No errors in the apache log.
-
If you are using suPHP then it would be writable so long as owner is writable.
Setting the file to 444 means that it is read only for everyone, including the owner, and the install still reports it as writeable so I'm not convinced that the check is working correctly on that front.
I will take out the system key code and let you know what happens.
-
As an aside, I think the installer needs a bit more work generally, after setting blesta-new.php permissions to 444 the installer still says that the file is writeable!
-
I thought blesta-new.php stayed there.
I have both blesta-new.php and blesta.php. But I suppose I just copy the files over when upgrading so that's probably why.
Looks like the file is just renamed, line 258 of app/controller/install.php
/** * Write the config file details * * @return false If the file could not be renamed (e.g. written to) */ private function writeConfig() { // Attempt to rename the config from blesta-new.php to blesta.php if (!rename(CONFIGDIR . "blesta-new.php", CONFIGDIR . "blesta.php")) return false; // Generate a sufficiently large random value Loader::load(VENDORDIR . "phpseclib" . DS . "Crypt" . DS . "Random.php"); $system_key = md5(crypt_random() . uniqid(php_uname('n'), true)) . md5(uniqid(php_uname('n'), true) . crypt_random()); $config = file_get_contents(CONFIGDIR . "blesta.php"); $replacements = array( '{database_host}' => $this->db_info['host'], '{database_name}' => $this->db_info['database'], '{database_user}' => $this->db_info['user'], '{database_password}' => $this->db_info['pass'], '{system_key}' => $system_key ); foreach ($replacements as &$value) { $value = str_replace(array('\\', '$', '"'), array('\\\\', '\$', '\"'), $value); } file_put_contents(CONFIGDIR . "blesta.php", str_replace(array_keys($replacements), array_values($replacements), $config)); return true; }Looks like the installer could possibly be falling down while trying to set up the system key, even if it couldn't do the variable replacement it would still return true, perhaps need another error check in there; being able to rename the file doesn't automatically mean that it was written successfully.
-
I'm guessing this was not compiled with suPHP?
Just to be clear..
1. Before install, you set the config directory to 777, and blesta-new.php to 666.
2. After you attempt to install it renames blesta-new.php to blesta.php but doesn't do tag replacement on database variables
Question: What are the permissions of blesta.php after it is renamed? Is it still 666 or something else?
If it's not writable by the web server at that point, my guess is that it may rename the file first and then attempt to do the variable replacements but it can't because it's no longer writable.
If this is what's happening, we should be able to look into a fix. Can you confirm?
Hi Paul,
SuPHP is actually active on this server and working normally for all other PHP applications.
The config directory is set to 777 and blesta-new.php to 666 before the install is attempted. The installer gives a pass to this requirement as well.
After the installation attempt blesta-new.php is renamed blesta.php, the permissions stay at 666 but no tag replacement is done at any level; this includes the database details but also the system key.
-
The error message in the screenshot you uploaded says that blesta-new.php isn't writable. Make sure it's writable by the webserver. If it's a cPanel account then usually the owner:group would be the username of that account.
With respect, I'm an advanced user who has been using Blesta since 2009 so I do know what I'm doing. The config/ directory is set at 777 and blesta-new.php is set at 666.
Also, if the directory and file wasn't writeable why allow the installer to say that it is a pass in the minimum requirements section of the installer as I posted earlier?
-
Erm I would try removing blesta.php, remove database, remove user, remake them both, connect them both and try again, http://yourdomain.com/install/
If that fails I'm confused.
Same result unfortunately. This install is being attempted on a bog standard cPanel server that fits the requirements, nothing custom or special. It seems like the installer is falling down at the config writing step, and there doesn't appear to be a failback in place to allow the user to download and upload the config file and then carry on with the install.
Disappointing, sure the developers will get it improved though.
-
Hi Tyson,
Can you compare the content in blesta-new.php with blesta.php? What are the differences, if any?
What OS and version of PHP are you running?
Both files are identical, only change is the installer has renamed the file but done nothing after that.
OS is CentOS 6.4, PHP version is 5.3.27.
-
Also happy to allow access to the system/install if required to debug the issue by the developers.
-
Just to add, the database appears to have been fully populated, from accounts_ach to user_otps, 94 tables in all.
-
Have listed the install screen below
Minimum Requirements: PASSPHP version 5.1.3 or greater is required. Your version: 5.3.27. PASS
The PDO extension is required. PASS
The pdo_mysql extension is required. PASS
The curl extension with a minimum version of 7.10.5 is required. Your version: 7.24.0 PASS
The openssl extension with a minimum version of 0.9.6 is required. Your version: 1.0.0 PASS
The ionCube Loader extension is required. PASS
The config file (/home/forumdoc/my/public_html/config/blesta-new.php) and directory (/home/forumdoc/my/public_html/config/) must be writable by the webserver (you can change these back after installation is complete). PASS
Recommended Requirements: PASSFor best results, PHP 5.2 or greater is recommended. PASS
The mcrypt extension is recommended for better performance. PASS
The gmp extension is highly recommended for better performance. PASS
The json extension is recommended for better performance. PASS
For better performance ensure that /home/forumdoc/my/public_html/cache/ is writable by the webserver. PASS
For best results a memory limit of at least 32M is recommended. Your setting: 128M PASS
For added security, 'register_globals' should be disabled. PASS
The imap extension is required to send and receive mail via SMTP and IMAP. PASS
The simplexml and libxml extensions are highly recommended as they may be required to interface with some systems. PASS
The zlib extension is highly recommend for better performance. PASS
Have run the install again and getting the message that the configuration file has been written. blesta-new.php has been moved to blesta.php however the database details have not been entered.
Configure::set("Blesta.database_info", array( 'driver' => "mysql", 'host' => "{database_host}", //'port' => "8889", 'database' => "{database_name}", 'user' => "{database_user}", 'pass' => "{database_password}", 'persistent' => false, 'charset_query' => "SET NAMES 'utf8'", 'options' => array() ) ); -
What PHP version / Mysql version did you have?
It worked fine on my server in the video.
PHP 5.3.27
MySQL 5.5.32
-
Hi all,
Really looking forward to trying v3, been around since early on v2. Have installed and got to the initial setup screen, filled out the relevant details however it is just throwing a blank page after submitting the form. Have attached the error_log that was in the root directory.
Cheers,
Mark
-
Have had exactly the same issue when installing 3.0.0 - all permissions were checked but the installer threw an error about blesta-new.php not being writeable, however the DB had been populated and once I'd written the config file manually I was able to carry on with the initial setup screen.
Deleting TLDs
in Support
Posted
Hi all,
There doesn't seem to be an option to delete TLDs in the Domain Manager on Blesta 5.5?
I'm on the TLD pricing page and although there is the option to disable there isn't an option to delete? I'm imported quite a few TLDs that I don't want to offer and would like to tidy this up by deleting them rather than disabling them, is this possible?
Happy to remove direct from the database if this is the only option but wanted to make sure that this won't affect any other systems.
Cheers,
Mark