Skip to content

cambell-prince/frontaccounting-theme-bootstrap

Repository files navigation

Bootstrap Theme for FrontAccounting

This project provides a Bootstrap 3 theme for FrontAccounting.

The theme is intentionally minimalist, following the default Bootstrap 3 theme. This provides a nice base for developing a range of more appealing themes.

Demo Site

The easiest way to have a look at the theme is to browse the demo site.

Have a look, its mostly functional - though not completely. Check out the known issues documented below and file a bug if you think you've found something we should know about.

Current Status

Its new, and largely funcitonal. However, its not 100% complete, so you can expect to find a few rough edges. Have a look at the 'known issues' documented below.

Up to the minute status can be found on our Trello board.

Known Issues

  • Drill down reports don't work.

Installation

Currently, er, you can't. Try the demo site instead.

Not happy with that? Well obviously it can be installed. The demo site is working. So if you're a developer...

Developer Installation via git

  • Install my feature/theme branch of FrontAccounting via git.
    • git clone https://github.com/cambell-prince/frontaccounting-theme-bootstrap.git
    • git checkout feature/theme or git checkout master-cp
  • Install this theme in the themes/bootstrap folder.
    • cd themes
    • git clone https://github.com/cambell-prince/frontaccounting-theme-bootstrap.git bootstrap
  • Run composer install to install the dependencies.
    • cd bootstrap
    • composer install

User Installation via tar or zip packages

  • Download one of the all in one packages, either the tgz or zip format.
  • Extract the contents of the package into your web root directory.
  • Run the FA installer as usual.
  • Select the bootstrap theme from the Setup | Display Setup page.

Filing Bugs

If you've found an issue that isn't already known do file an issue in the issue tracker.

But first...

  • Check that this is not a known issue.
  • Check that the issue has not already been filed by someone else. Otherwise we have to mark it as a duplicate, point you to the duplicate. Its a pain for you a pain for us, so do check first :-)

And then...

Telling us...

  • The url that you accessed (copy it from the address bar)
  • The error message if any. Include a screen shot would be nice.
  • A brief statement of what you expected to see.