FutureSight Technologies

fire219

jvvg wrote:
fire219 wrote:
jvvg wrote:
fire219 wrote:
The link to the SQL file in the instructions (for the new beta FBB) is broken.
Oops. I forgot to migrate that to the new website.

It should work now.
*sigh* Apache's throwing HTTP 500s at me…. it's progress I guess
What's in your .htaccess file? Make sure all of the commands and stuff are valid.

Also make sure that the RewriteEngine is enabled. That was a problem for me when I tested it out.

I'm using the exact .htaccess that the install guide gave me.

I did not have the RewriteEngine on, but now that I do, it still errors out (same HTTP 500).

However, looking in apache's error log, I find:

[Fri May 24 19:46:21 2013] [alert] [client 192.168.0.25] /var/www/forums/.htaccess: RewriteBase takes one argument, the base URL of the per-directory context

jvvg

fire219 wrote:
jvvg wrote:
fire219 wrote:
jvvg wrote:
fire219 wrote:
The link to the SQL file in the instructions (for the new beta FBB) is broken.
Oops. I forgot to migrate that to the new website.

It should work now.
*sigh* Apache's throwing HTTP 500s at me…. it's progress I guess
What's in your .htaccess file? Make sure all of the commands and stuff are valid.

Also make sure that the RewriteEngine is enabled. That was a problem for me when I tested it out.
I'm using the exact .htaccess that the install guide gave me.

I did not have the RewriteEngine on, but now that I do, it still errors out (same HTTP 500).

However, looking in apache's error log, I find:
[Fri May 24 19:46:21 2013] [alert] [client 192.168.0.25] /var/www/forums/.htaccess: RewriteBase takes one argument, the base URL of the per-directory context

What is the RewriteBase directive set as in the .htaccess?

fire219

The whole .htaccess file is

RewriteEngine On
RewriteBase /

RewriteCond %{REQUEST_FILENAME} -f
RewriteRule ^static/(.*)$ static/$1 [L]

RewriteRule ^(.*)$ dispatcher.php [L]

AllowOverride All

jvvg

fire219 wrote:

The whole .htaccess file is

RewriteEngine On
RewriteBase /

RewriteCond %{REQUEST_FILENAME} -f
RewriteRule ^static/(.*)$ static/$1 [L]

RewriteRule ^(.*)$ dispatcher.php [L]

AllowOverride All

If your forums are at /forums (which it looks like they are from the error log), then you just need to replace the RewriteBase directive with

RewriteBase /forums

fire219

jvvg wrote:
fire219 wrote:
The whole .htaccess file is
RewriteEngine On
RewriteBase /

RewriteCond %{REQUEST_FILENAME} -f
RewriteRule ^static/(.*)$ static/$1 [L]

RewriteRule ^(.*)$ dispatcher.php [L]

AllowOverride All
If your forums are at /forums (which it looks like they are from the error log), then you just need to replace the RewriteBase directive with
RewriteBase /forums

Apache's still not happy, HTTP500 as usual….

This time, the error log says that “AllowOverride” is not allowed in an htaccess file. So I took it out, and there's progress!

(I refuse to use tinypic or photobucket…..)

jvvg

fire219 wrote:
jvvg wrote:
fire219 wrote:
The whole .htaccess file is
RewriteEngine On
RewriteBase /

RewriteCond %{REQUEST_FILENAME} -f
RewriteRule ^static/(.*)$ static/$1 [L]

RewriteRule ^(.*)$ dispatcher.php [L]

AllowOverride All
If your forums are at /forums (which it looks like they are from the error log), then you just need to replace the RewriteBase directive with
RewriteBase /forums
Apache's still not happy, HTTP500 as usual….

This time, the error log says that “AllowOverride” is not allowed in an htaccess file. So I took it out, and there's progress!

(I refuse to use tinypic or photobucket…..)

The AllowOverride directive needs to be set in the site definition, not the .htaccess file. If you haven't done extensive server hacking, it's available at /etc/apache2/sites-enabled/000-default . Find every occurence of AllowOverride in it and set them to all, and remove it from the .htaccess file.

Basically just search for “AllowOverride None” in it and replace all occurrences with “AllowOverride All”

Last edited by jvvg (May 25, 2013 14:05:53)

jvvg

If you want to see how much progress we've made on FutureBB since the beta release, check it out here.

jvvg

Little update on FutureBB:
For version 1.0, we had 39 development tickets total. Currently there are 5 left.

Features implemented since last status update

Searching trash bin
Extension system
Showing post count in posts (if admin enables it)
Forum rules that users registering must agree to

Features left to code

Allowing admin to upload custom logos and favicons
A few small issues with smileys
Language packs
Making a real installer

jvvg

FutureBB is almost done. We just need to finish testing everything.

However, unfortunately, I am on vacation right now and will be for the next two weeks or so, so I can complete the testing but won't be able to prepare everything for release until I return.

The following things have been done since my last post:

Better trash bin searching
Posts can't be larger than 256 KB
Signature size can be limited in the following ways: pixel height, text length, and number of lines
No more inline CSS (i.e. easier to make customizable styles)
Multi-language support (currently we only have a pack for English, but plan to make ones for Spanish, French, and Italian)
Trash bin shows original poster for deleted posts
You can upload your own favicon on the style settings page
There is a database abstraction system, so implementing SQLite will be much simpler in version 1.1
The installer is now built in to the software again (rather than that web utility), but much less likely to fail
You can add custom header links

The following features are planned for version 1.1:

SQLite support
Better organization of admin panel
RSS feeds
Porting all existing queries to the new database abstraction system
Language packs for Spanish, Italian, and French
Warning system (extension)
Direct image uploading (extension)

jvvg

More updates to FutureBB!

Since the last update, here's what's new:

Bug with link to user list fixed
Silent edits
Major interface and style improvements by LS97
Showing post number in post header
Trash bin orders topics by date deleted

The following features were added to be worked on in version 1.1:

Easy embedding of threads in other sites and having a reply box
Show avatars instead of names in online list if enabled
Link to show new posts on topics

jvvg

So FutureBB is almost done now. It will be released later this week (probably Thursday or Friday). All that's left is one minor feature, and finding as many bugs as possible. To see what is already there from the point of view of a regular user, check out our forums. We will post a few screenshots of admin stuff throughout the week.

mythbusteranimator

It's awesome!

jvvg

As promised, here are some admin screenshots:

mythbusteranimator wrote:
It's awesome!

Thanks!

jvvg

Everything appears to be working, so FutureBB will be released in the evening (Scratch Time) tomorrow!

nathanprocks

jvvg wrote:
Everything appears to be working, so FutureBB will be released in the evening (Scratch Time) tomorrow!

Cool. Does it have an API for logging into the forums from the main website?

jvvg

nathanprocks wrote:
jvvg wrote:
Everything appears to be working, so FutureBB will be released in the evening (Scratch Time) tomorrow!
Cool. Does it have an API for logging into the forums from the main website?

No, but it is fairly easy to make one. Just include the file {FORUM ROOT}/app_resources/includes/startup.php, and then the variable $futurebb_user contains all relevant information to the current forum user. That's what we use on the FutureSight website (a few main site features, such as product ratings and administration tools, rely on that).

nathanprocks

jvvg wrote:
nathanprocks wrote:
jvvg wrote:
Everything appears to be working, so FutureBB will be released in the evening (Scratch Time) tomorrow!
Cool. Does it have an API for logging into the forums from the main website?
No, but it is fairly easy to make one. Just include the file {FORUM ROOT}/app_resources/includes/startup.php, and then the variable $futurebb_user contains all relevant information to the current forum user. That's what we use on the FutureSight website (a few main site features, such as product ratings and administration tools, rely on that).

Ok. I may use it when I can be bothered to work on my website next… I might wait a while because I haven't had access to the Internet at home for a while because my mum can't afford it at the moment.

jvvg

We're now just doing some last-minute bug checking before the release. Everything is going to plan, so the software will be released tonight (Scratch Time).

jvvg

FutureBB 1.0 has been released! You can download it on its product page on our website. Unlike the beta, this one is very easy to install. I got it up and running on my raspberry pi test server in under five minutes (and two of those minutes were spent deciding a database password).

All you need is an Apache or nginx server with PHP and MySQL (SQLite will be supported in version 1.1). We can assure you it is worth your time to install. Once you start using FutureBB, you will never want to use any other forum system.

Even better, we are also making a tool to copy information from other forum systems and convert it into FutureBB format, so changing systems to FutureBB will be even easier.

fire219

Yay!

Actually… not yay. After I finished the install, nginx refuses all HTTP requests, even if I switch to apache… I have no idea how or why. Maybe I did something stupid.

Discuss Scratch