wfitg

Exactly. And that is what I am suggesting. Rather than add more and more features to the Blesta core (and make Blesta bloated like the others), just make a simple plugin to do that one feature. That way the people who do not need that feature do not have to add it to their blesta installation. This would keep Blesta light weight.

You are misunderstanding. For example, a wordpress plugin could add Google maps to a page without changing the Wordpress core or theme files. Its only function is to embed a map in to a page. A blesta plugin could be made to do something like turn on and off VAT on the form without having to change the core or add that feature to the core files. Back in that day there was something called an "include" that would include code from from a file that was not part of the originl framework. Dreamweaver may even still use includes.

I'm talking about expanding that concept. After the billing plugin is installed more features can be added or taken away. IOW make Blesta run more like Joomla, or Wordpress. It is remarkable how each Wordpress or Joomla site can be made different with the use of seperate plugins that are easily turned on and off, or deleted and added. Blesta is already superior, but could be made more-so with the use if individual feature plugins. Some of them can be commerical, some for free. They can be community supported or Blesta sponsored.

Ok, thanks.

The reason why i switched to Blesta was because it is not bloated. It had a modern and easy to use management console with the exact features I thought were needed. Therefore, rather than have hundreds of new feature requests being added to the core would it not be better to make some of these additional new features as seperate modules that can be added as needed? For instance, if someone wants to have a feature that automatically deletes services after they have been suspended for 90 days, they can download a small plugin giving them that feature. (this is just an example) Thoughts everyone?

I applied the hot fix once, but since then i have upgraded Blesta to the new beta. Does the hotfix have to be applied again after ungrading to the newest version of Blesta beta? Or has it already been added to the newst version?

I do not understand. I run 5.4.31. Blesta works fine.

Well, the lable says <label for="tax_id">Tax ID/VATIN</label> Many would not confuse Tax ID number with SSN. But many would. Here is a tread asking that very question: "I was going to sign up for pepperjam and it wanted my tax id number. Isn't that my social security number? Thanks." http://www.abestweb.com/forums/ebay-enterprise-affiliate-network-480/my-tax-id-number-my-ssn-137413.html "The IRS, or Internal Revenue Service, keeps track of the money earned by individuals and businesses in the United States. It tracks income by an identifying number, typically your Social Security number -- a number assigned to individuals -- or Federal Tax ID number, also called an Employer Identification Number (EIN) -- assigned to businesses or organizations." People who do not own a business are use to using their SSN as a Tax ID on Government forms. So there is where some confusion take place. But like you said, Blesta already has a plan to make it optional.

I like this idea better. Sticking as close to the original code without too many changes is always best.

OK thanks. I'll try this soon. I have it downloaded.

I like the idea. But I don't like having to set some file permissions 777

This looks great. the only thing that I do not like is having to set some file permissions 777

To use vQmod insert in the template: $var = 'Remove client tax ID field'; correct?

IMHO the problem is with the wording. If the label said: VATAN (where applicable),I don't think many users would have a problem with it. People in America and other places use their social security number as a "Tax ID". Users think we are asking for their social security number to register. I have never been asked to gave my social security number to buy something on the Internet. Ebay, Amazon, none of them ask for a tax-id or SSN to make a purchase. No one wants to list their social security number unless it is an absolutely necessary. Web-hosting does not qualify as "needing to know" someone's social security number. Some users could misunderstand the form and think we are scamming them just to get their financial information.

This is good too. But I'm talking about a menu on the user side.

Exactly. A public facing menu that matches the main website. I had installed a jQuery responsive menu in the blesta template at the top, but it vanished.

I would like to suggest a menu plugin for Blesta. It would be used to help clients navigate outside web pages. For instance, the menu could allow clients to return to the home page of a Wordpress, or go to the Wordpress contact page, etc...

I think the Blesta coloring scheme works nice for matching something like a Wordpress Installation. That is what I have done. However, it would also be nice to only integrate a Wordpress Menu in to the Blesta. This way clients can navigate back to specific pages on the website too. When you have time, can you make a tutorial on that?

This is a GREAT tutorial mate! Thanks for making this. I'm going to try it

I like the ones that say they are from the FBI. heh...

I did modify it, but can restore it. I recently asked for a Belesta developer licence so I can run a local copy. I plan to tinker around with it. Learn my way around and install NetBeans Thanks for this great example

Thanks! I'll check this out soon

No, but I am still learning. Some of this is new territory for me

For those who like to keep everything updated and patched: Security Fix: Swiftmailer 5.2.1 released http://blog.swiftmailer.org/ These days Spammers troll the Internet looking for venerabilities.

Did'nt work, but thanks. However, adding this did, I used it as a workaround, for those people searching: structure.pt <a href="index.html"> <img src="https://wfitg.com/img/small-logo3.png" alt="logo" class="emailImage" /> </a> the css: @media only screen and (max-width: 480px) { .emailImage{ height:auto !important; max-width:600px !important; width: 100% !important; } }