mrrsm

Namecheap works fine for me. Make sure you have allowed your ip address (the ip address for blesta) in the namecheap api section. Past that you should get an error message in the log if it isn't going though.

+1 it would make it so the customers I have that are using DO could have things automatically working rather then me having to manually manage them.

php 5.4 added square bracket array notation (http://php.net/manual/en/language.types.array.php)

I did some brief searching and could find any threads even though I thought this was talked about before. There should be a way to print out a current statement for a customer. For example if they have 2 invoices, 1 is partially paid, I should be able to print out a statement that shows the total from both invoices minus the amount paid and the total they owe. I looked in reporting and couldn't find anything either although I would figure I would find this on the clients page in the admin section.

You should add the package_id=# field to your urls for your plans. That way when they select one on the main site it will have the proper one selected on the billing side.

I think that there are good ideas here, it seems like the main issue may be in support as you may want to hire support people to manage all the companies at once. If the support manager could combine all of the relevant customer data for the companies they have permission to see they could manage everything in one place. Personally I would want to have billing, transactions, etc separate but having the combined support would be useful. Edit: maybe even a special support plugin for multi-brand installs to do this

I would like a way to toggle the "AddFreeWhoisguard" on domain creation (as seen here: https://www.namecheap.com/support/api/methods/domains/create.aspx) I would want to be able to add it for every domain and be able to enable it through a toggle in the admin section to start. In the long run I would like to be able to tie it to an addon during checkout.

That works for me, if you had a reason I was all ears as sometimes I get a bit of tunnel vision and don't see obvious alternatives.

What benefit does manually adding them rather than using the api to get the current list that they offer have? If you use the api you know they are valid, if you do them manually they may not be valid (or you still should validate them with the api).

You would still have to select which ones you want to sell, this would just get the ones that are available through your registrar when you create the package.

+1 I run into this support ticket on occasion, having a more prominent way to order new services would be great.

I believe all the domain reseller apis allow you to get a list of tld's that are available. Rather then having them hard coded why not pull them once a day during a cron job and cache them. This way all I would have to do is add a new package if/when a new gtld comes out.

In theory you could store the private key in the database and that would be just as secure as storing the password there. (Assuming it is encrypted) My ssh is already locked down to known ip's via firewall and my backup user is very locked down as to what they can do anyways.

I try and use keys as much as possible so this would be nice to have as I was using sftp as a secondary backup to the Amazon backups.

This is my full nginx conf on my dev install server { listen 80; server_name DOMAIN; access_log PATH; error_log PATH; root PATH; index index.php; # serve static files directly location ~* \.(jpg|jpeg|gif|css|png|js|ico|html)$ { access_log off; expires max; } # enforce NO www if ($host ~* ^www\.(.*)) { set $host_without_www $1; rewrite ^/(.*)$ $scheme://$host_without_www/$1 permanent; } # catch all error_page 404 /index.php; location ~ \.php$ { fastcgi_index index.php; fastcgi_pass php; include fastcgi_params; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_param SCRIPT_NAME $fastcgi_script_name; } location / { server_tokens off; client_max_body_size 20m; client_body_buffer_size 128k; try_files $uri $uri/ /index.php?$args; } } My fastcgi_params had a small change as well fastcgi_param QUERY_STRING $query_string; fastcgi_param REQUEST_METHOD $request_method; fastcgi_param CONTENT_TYPE $content_type; fastcgi_param CONTENT_LENGTH $content_length; fastcgi_param HOSTNAME $hostname; fastcgi_param SCRIPT_NAME $fastcgi_script_name; fastcgi_param REQUEST_URI $request_uri; fastcgi_param DOCUMENT_URI $document_uri; fastcgi_param DOCUMENT_ROOT $document_root; fastcgi_param SERVER_PROTOCOL $server_protocol; fastcgi_param HTTPS $https if_not_empty; fastcgi_param GATEWAY_INTERFACE CGI/1.1; fastcgi_param SERVER_SOFTWARE nginx/$nginx_version; fastcgi_param REMOTE_ADDR $remote_addr; fastcgi_param REMOTE_PORT $remote_port; fastcgi_param SERVER_ADDR $server_addr; fastcgi_param SERVER_PORT $server_port; #fastcgi_param SERVER_NAME $server_name; fastcgi_param SERVER_NAME $host; I don't see any other changes I may have made.

Here is my \.php section and basic rewrite section. These are working for me. I would post my entire config but it is huge right now as I have a lot of other directives for other things as well. If this doesn't help I can look a bit more after lunch and make a basic nginx config. location ~ \.php$ { try_files $uri =404; # Tweak for Nginx to work with PHP from vendors fastcgi_split_path_info ^(.+\.php)(/.+)$; # NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini fastcgi_connect_timeout 60; fastcgi_send_timeout 180; fastcgi_read_timeout 180; # Buffer settings increase to compensate for increased time/size due to SSL fastcgi_buffer_size 128k; fastcgi_buffers 4 256k; # fastcgi_busy_buffers_size 256k; fastcgi_temp_file_write_size 256k; fastcgi_intercept_errors on; fastcgi_pass php; fastcgi_index index.php; include fastcgi_params; } location / { error_page 404 = @blesta; #IF file doesn't exist log_not_found off; } #Core rewrite location @blesta { rewrite ^(.*)$ /index.php last; }

What do you currently have for your nginx config? If you are using fastcgi you may be always calling index.php so it adds it thinking that was the original request.

Add the ability to move a predefined response into different folders without having to do a create and delete.

Then a feature request shall be made.

Is there a way to move a predefined response into a different folder without having to recreate it in the support manager?

I know namecheap has the getPrice api call (https://www.namecheap.com/support/api/methods/users/get-pricing.aspx) Looking at the enom api it looks like this may get the info: PE_GetProductPrice I may be wrong though as I just did a quick search and didn't read into it too much.

I think this applies to all the domain reseller modules.

I like this, When you have more then would fit in the width it could add little arrows which would scroll the tabs side to side. As long as I could order them it would work perfect for me.

I really like this idea and believe you should open this as a separate feature request. (Otherwise I may do it next week). Being able to email/print an account statement as a customer or for a customer would be very useful.

+1 as I had thought this was happening but wasn't.