PortCTL Systems | Billing Software

[PortCTL]

Hello,

Months ago, a few developers including myself started working on PortCTL Billing Panel. We originally intended to use it for ourselves, however feel it would be much better if we open-sourced it, and that's what we plan on doing, but first we must finish off the very last core module, which is Live Support.

Unlike regular billing softwares, since we are new, we only support PayPal payment for processing of invoices. Additionally, we have not written the cPanel module yet, nor SolusVM module. If you would like to give us a hand, it will be published on Github once we finish the final core module.

One of our main goals is to make sure your workspace isn't crowded. Therefore, as you'll see in the screenshots below, we ensure everything looks clean, and is ready to be expanded on at free-will.

Now, for screenshots! Note: All content in panel is merely placeholders for future content.



















Administration Panel: http://imgur.com/swhWspq,HsKZ2GT,voVrJUg,7mH9wcI,lgJY8nU,SnI8qY3

Customer Panel: http://imgur.com/JEcaKSA,Vi28m8w,Sf8H6cN,P2jmKxa,RaGmVqE,z4hQV7I

Just to answer some common questions:

1. Is there any framework used? There is no framework used

2. Theme is? For the frontend theme displayed, and the admin theme displayed, we use Porto Theme, found on themeforest

3. Licensed under? MIT License (reference: http://choosealicense.com/licenses/mit/)

There is no official live demo yet, however I will update once one is up and running.

Have any questions? I'd be happy to answer them.

 

[KuJoe]

I can port my Interworx, cPanel, and Bitpay modules I created for my own script over once you get it on GitHub. I can also port my FraudRecord module over if you're script supports it.

EDIT: I just realized I used the word "port" twice not even noticing what the name of the software is. LoL.

 

[PortCTL]

I can port my Interworx, cPanel, and Bitpay modules I created for my own script over once you get it on GitHub. I can also port my FraudRecord module over if you're script supports it.

Sounds good, I'll send you a message once it's up on github.

 

[KuJoe]

Sounds good, I'll send you a message once it's up on github.

Thanks. Glad to see a project like this. I was going to release an open source billing script, but decided against it due to my lack of time to support it properly so I'd be happy to contribute to another project instead.

 

[PortCTL]

Thanks. Glad to see a project like this. I was going to release an open source billing script, but decided against it due to my lack of time to support it properly so I'd be happy to contribute to another project instead.

Cool, well we appreciate all the contributions we can get to make this a better, widely-available and used billing software. It'll be synced up on github publicly within the next few days, and I'll also be putting up a live demo for everyone to test, and play around with the software.

 

[drmike]

Interesting project.

How soon, realistically before you push source to public?

 

[telephone]

2. Theme is? For the frontend theme displayed, and the admin theme displayed, we use Porto Theme, found on themeforest

Before you go public, you'll need to release with a different theme. Themeforest's themes are not distributable via open source software without prior permission. You can purchase an extended license, but even that can be a grey area as you're basically giving their theme away for free (if you include source files).

 

[fixidixi]

@telephone:

Are you sure?

Regular: Use in a free end product (more than one end user allowed)

source: http://themeforest.net/licenses/standard

 

[PortCTL]

Before you go public, you'll need to release with a different theme. Themeforest's themes are not distributable via open source software without prior permission. You can purchase an extended license, but even that can be a grey area as you're basically giving their theme away for free (if you include source files).

After contacting the publisher, I received a response that stated that I'm allowed to release it, as long as it's not sold in a paid product. Additionally themeforest licenses state that "Regular: Use in a free end product (more than one end user allowed)." Therefore there is no issues with release the script open-source.

 

[PortCTL]

Interesting project.

How soon, realistically before you push source to public?

About 3-4 days, currently trying to get some servers up for hosting demos, etc.

 

[telephone]

@telephone:

Are you sure?

Regular: Use in a free end product (more than one end user allowed)

source: http://themeforest.net/licenses/standard

Yes. A regular license does not include re-distribution of source files.

The point you quoted refers to access to the product. As in multiple users can access my site for free (sign-up/login with no charge). At no point do they receive the source files. Here's a quote from their FAQ:

Which license do I need for an end product that is freely accessible or freely distributed to users?

 

As long as the end users can freely access the end product, the regular license is fine. There can be more than one end-user (the person who uses the end product, such as the end consumer) as long as there is only one, unique end product.

Example: A flyer that you freely give out or a YouTube video that's free to view

Licensing and OSS are always tricky, that's why it's best to ask permission beforehand. As when you think about it, you're hosting their code for free on Github which can upset a lot of authors.

After contacting the publisher, I received a response that stated that I'm allowed to release it, as long as it's not sold in a paid product. Additionally themeforest licenses state that "Regular: Use in a free end product (more than one end user allowed)." Therefore there is no issues with release the script open-source.

+1 for getting permission  B).

 

[PortCTL]

Thanks to @AshleyUK (zxplay) we are syncing a live demo currently. Will update with demo URL and credentials.

Things to note about the demo: Username and passwords are automatically mailed out to customer, if you don't get an email from the demo box, use the default demo credentials.

 

[PortCTL]

The demo is live.

Main site: http://136.243.247.11/

Client area: http://136.243.247.11/clients/

Admin area: http://136.243.247.11/admincp/

Admin credentials:

USER: demoadmin

PASS: demo123!@

Sample Customer credentials:

CUSTOMER ID: 14236897603

PASSWORD: demo123!@

CUSTOMER EMAIL: [email protected]

If you have located a bug, please email [email protected]

Be aware, the error "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near LIMIT 1" is not a real error, it is very simply a honeypot to automatically log hacking attempts, and start blocking IP addresses of automated exploit attempts.

 

[d2d4j]

Hi portctl

Kudos to you, it looks lovely.

Is there any reason why you have not set https access (I'm thinking you may not have a paid SSL)

I have had a quick look, and noted some things, not really bugs but I only looked quickly.

In whmcs, you cannot view source code from browser, adding users from admin does not appear to work, I presume this is because it is a demo etc... Same with changing password, which then shows users as edit 0 and edit 0 for admin and demoadmin

If you want a test on interworx cp, I could let you on our interworx test server.

Many thanks

John

 

[PortCTL]

Hi portctl Kudos to you, it looks lovely. Is there any reason why you have not set https access (I'm thinking you may not have a paid SSL) I have had a quick look, and noted some things, not really bugs but I only looked quickly. In whmcs, you cannot view source code from browser, adding users from admin does not appear to work, I presume this is because it is a demo etc... Same with changing password, which then shows users as edit 0 and edit 0 for admin and demoadmin If you want a test on interworx cp, I could let you on our interworx test server. Many thanks John

Hello,

Thanks for that information, we disabled some features just so everyone get's a fair chance to play around with the demo. As for SSL, we do have a SSL cerificate on our main website, which is under construction.

If you would like to offer us access to testing places, please email [email protected] with information.

Additionally, the source code is published, and am aware for 3 bugs that exist currently, and am working to fix them. https://github.com/IOTechCH/portctl is the github link.

 

[d2d4j]

Hi

Sorry just one more whilst I remember

Where do you set the taxation % for calculation and does it allow different countries taxation which came into force January this year

Many thanks

John

 

[PortCTL]

Hi Sorry just one more whilst I remember Where do you set the taxation % for calculation and does it allow different countries taxation which came into force January this year Many thanks John

No, that isn't in yet, it is planned though.

 

[Prestige]

I see you're storing MD5 passwords into the database, and then verifying them by a query.

You can easily use password_hash and then password_verify it when logging in (if PHP 5 >= 5.5.0), else use https://github.com/ircmaxell/password_compat.

 

[PortCTL]

I see you're storing MD5 passwords into the database, and then verifying them by a query.

You can easily use password_hash and then password_verify it when logging in (if PHP 5 >= 5.5.0), else use https://github.com/ircmaxell/password_compat.

Thanks for suggestion, I'll implement that in the next update. Just starting to work on a templating engine.

 

[devonblzx]

Be aware, the error "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near LIMIT 1" is not a real error, it is very simply a honeypot to automatically log hacking attempts, and start blocking IP addresses of automated exploit attempts.

Looks interesting.  I'm curious why you would need to display an error to "log hacking attempts".  This is obviously just an error showing one of your queries is using an invalid syntax, most likely with LIMIT in the wrong place.   As a developer myself, there should be no reason for you to purposefully display a MySQL error to an end user.  Any sort of logging should be done behind the scenes.