Frequently Asked Questions (FAQ)

What is WEBvivo?

A software tool for making websites simple or complex, secure, fast and with reduced development time and cost, designed for programmers (non-end users).

He's got a little of these concepts:

  • RAD: Rapid application development
  • CMS: Content management system
  • WAF: Web Application Framework
  • KISS: Keep It Simple Stupid

How does it work?

  1. You install WEBvivo; The result is an operational website, with a template and a backend.
  2. You edit the template (skeleton) and the home page that are installed as an example to adapt it to your needs.
  3. You create new pages from the backend.
  4. You add your own code, without worrying about managing any of this:
    • Pages
    • Permits
    • Users
    • Languages
    • Texts
    • Configurations
    • And much more....

What are your requirements?

  • PHP 5.6 or later
  • MySQL, MariaDB, Percona (recommended MariaDB 10 or later)
  • WEB Server. Only tested with Apache although it probably works on Nginx and IIS.

Why another framework if there are lots of them?

The first version of WEBvivo is from April 2002, then there were none of the current framewoks, so it is not one more. We have simply used it for years for our own developments without making it public.

How much does WEBvivo cost?

It seems that what is free does not cost, but SLOCCount says that the development cost $944,900 USD (about 767,000€). It may not be the best software in the world, nor the most expensive, but we don't charge licenses. WEBvivo is open source (free of charge), but without any guarantee. If you need support and guarantees, you can request a private license, ask us for a quote if you are interested.

Will I be able to get support in the future?

We have been improving WEBvivo for 17 years and have no plans to stop. Version 3 will be published with an open source license on our GitHub page. From that moment anyone can fork it and make their own developments. Among our short-term plans is to create a support platform for developers on this website.

What makes WEBvivo different?

It is focused on writing the code you need and solves many of the common tasks in web site development.

It has libraries to manage, among other things:

  • Virtual Pages
  • Users
  • Permits
  • Texts (206 languages preinstalled)
  • Rich text blocks
  • Contacts
  • Shopping cart
  • Product Management via EAV
  • Payment gateways
  • Configuration Keys
  • Multi-site and multi-template
  • Banners, advertisers, click tracking and views with statistics
  • News and Events
  • Download and tracking of documents and images
  • Image manipulation
  • Accesses
  • Cache
  • And more....

Why is it faster than other solutions?

  • We don't use additional presentation layers like Smarty (we actually hate Smarty), PHP already integrates well with HTML.
  • We don't use hooks because there are no third-party plugins, if you need something you must write a class (we have already said this is for programmers)
  • We have reviewed the code over and over again to improve the loading speed.

Is WEBvivo safe?

The only thing certain in life is death, but one of the leaders of this project is an "obsessed" security consultant. There is no architecture or code made without carefully reviewing its security.

How do I start using it?

The first thing to do is to install it.

WEBvivo consists of two parts, a library in the directory normally used by the Pear libraries that can be used for all the websites of the same server and an installation for each website that has between 22 tables and more than 80 (depending on the functionalities).

In theory it is possible to use the part of the library installed in the web itself, for example in the level before public documents, since there is not even a single absolute path, all paths are handled with self-calculated variables, but we haven't really tried it.

Once installed, you already have an operative website with backend, from that point on you only have to write your code. The process is very fast, but unfortunately we don't have an installer yet, so you'll have to follow the instructions and possibly read at least some of the documentation to boot.