FusionBB
FusionBB Review (large)
Recent Members
Welcome them to our community!
FusionBB SWAG!

FusionBB golf shirts, t-shirts, mousepads and more.

Recent Topics
Tagging
FusionBBDev Recent Topics

Username Topic: Exciting News - New Project Manager for FusionBB
JoshPet
FusionBB Developer
Total Posts: 6722
*
Birthday: 02-08 
Location: Charlotte, NC
Average Post Ranks%:                       
- Post#85994    



Hey Everyone,

As many of you are aware, our development schedule has been much slower paced than I would have liked. I take full responsibility for that, as since Couch left due to family reasons, I have been working on FusionBB by myself. With other obligations, and dealing with support questions, issues etc.... there ends up being little time to actually work on new development of features that FusionBB desperately needs to be competitive and keep our customers' sites competitive too.

I am pleased to announce, that we have a new Project Manager joining the team, who's sole focus will be the development of FusionBB. His name is Alex Ali and he has many years of experience in the forum world. Please help me welcome him to the team. He has many great ideas and lots of much needed vision for FusionBB, so I'm very excited to have him on board.

Don't worry though, I am not leaving, I will still be involved in the planning and development for FusionBB.



Feel Better, Feel Younger, Sleep Better - Trans-D Tropin
Visit www.BuyTransD.com - use coupon code 1004 to save $20
 
Username Topic: Emails to Block
JoshPet
FusionBB Developer
Total Posts: 6722
*
Birthday: 02-08 
Location: Charlotte, NC
Average Post Ranks%:                       
- Post#85646    



Let's use this post to share bad email domains that we know spammers are using to try to register.

To edit the bad emails, go into your admin panel, under Edit, and click Bad Emails

163.com
21cn.com
qq.com
sohu.com
tom.com
yeah.net



Feel Better, Feel Younger, Sleep Better - Trans-D Tropin
Visit www.BuyTransD.com - use coupon code 1004 to save $20
 
Username Topic: FusionBB Version 3.2 Released
JoshPet
FusionBB Developer
Total Posts: 6722
*
Birthday: 02-08 
Location: Charlotte, NC
Average Post Ranks%:                       
- Post#85417    



I am pleased to announce that FusionBB Version 3.2 has been released. It is available for download from the Member Area download forum. This is different from the way previous versions were downloaded, so click here if you didn't see the announcement about the license system.

For the most part, FusionBB 3.2 is a Minor Release and includes:
- Fixes some consistency issues between past versions
- Fixed some bugs when editing forums
- Fixed some bugs when managing attachments
- Fixed some issues with regards to post counts
- Added an HTML editor when editing site inserts and custom pages

Upgrade Instructions:
- BACKUP Your Files
- BACKUP Your Database
- Upload All Files
- Run /install/install.php in your browser

Professional Upgrade is available for $49 by clicking on the Purchase tab above.

Is this an amazing Kick A... Releas?
No, it's a minor release. There is not alot of new bells and whistles in it... yet. But here's the back story....

As many of you know, for years I have run FusionBB "on the side" while working a full time job. The last several years, Couchtomatoe has worked with us on coding. He did an awesome job and added some amazing things to FusionBB.

However, during his time helping, I was very busy with work and life etc... so honestly, my head wasn't in the day to day aspects of coding. I managed features and we talked about things etc....

Since his departure, I have spent some time re-engaging my head into the code. I've been working with some users on some support and bug issues. I've been getting my ducks in a row.

There has been a change in my work situation, which will allow me some more time to devote to FusionBB moving forward.

So why the release?
Sadly, in the past, we've had multiple versions of the same version. Meaning, we release 3.1 but then there's something wrong so some files got changed, and we repackaged and updated our package. Usually this was pretty quick, but the end result is you end up with multiple versions of each version, which should never happen. Because then someone is experiencing a bug in "3.1 Final 2" but not everyone has the same "3.1 Final 2" so headaches follow. LOL

Since 3.1 Final 2 got packaged multiple times, later versions of 3.1 Final 2 ended up having some of the 3.2 features and fixes in it. Sadly, since I wasn't "hands on" when all this was happening, I don't have a real clear idea of exactly what got included when. All I know from digging in to some people's issues, is that there are some consistency issues between the versions.

So my intention with releasing 3.2 is to set everyone with the same version. If I make any changes to it, it'll be 3.2.1 or 3.3 or whatever, but there won't be another 3.2.

Now that everyone's on the clean slate of 3.2, then we can begin working on some heavier features for what will be 3.3.



Feel Better, Feel Younger, Sleep Better - Trans-D Tropin
Visit www.BuyTransD.com - use coupon code 1004 to save $20
 
Username Topic: New License System & Development
JoshPet
FusionBB Developer
Total Posts: 6722
*
Birthday: 02-08 
Location: Charlotte, NC
Average Post Ranks%:                       
- Post#85387    



Hey Everyone,

Just a couple of quick notes.

License System
One, we were using a software package called phpAudit for our billing and license system. This was a separate system from the forum software, a commercial product we purchased. Our IP address changed recently, and the license for that software is tied to the IP address, and after WEEKS of round and round with them, they wanted me to buy the software again just because our IP address changed, which doesn't make any sense.

Since it wasn't the world's best system anyway - and actually confused alot of our users, I've decided to nix it.

I currently have setup a purchase option using the built-in MyPaymentPal functionality here in FusionBB. It was kind of a puzzle, but I was able to export purchase data and bring it into FusionBB.

So in our FusionBB Support Forums section, you will notice a new forum titled "Download Forum" right at the top. This forum contains the download files.

If your license is currently active, you will be able to access that forum. If it's not, then you will be prompted to renew via PayPal and get instant access to the download.

As I said, it was a puzzle importing the purchases from the phpAudit system and matching up to users in FusionBB. 95% of them matched based on emails used when you purchased. If you don't have access to that forum, and feel you should, please submit a ticket with the details of your purchase and we'll get that corrected for you.

Development
The big question.... development. With the departure of Couch development is going much more slowly... however it is progressing. I have been focusing on some bugs and some code cleanup. It's my *hope* (fingers crossed, spin around 3 times, spit over my shoulder, kiss a leprechaun etc...) that we will have the next release out yet this month. I appreciate your patience and in working with several customers directly the last few months I've been able to track down some troublesome issues which will have a positive impact on the next release.



Feel Better, Feel Younger, Sleep Better - Trans-D Tropin
Visit www.BuyTransD.com - use coupon code 1004 to save $20
 
Username Topic: How I would like to see Upgrades performed
Couchtomatoe
Code Monkey
Total Posts: 3049
*
Birthday: 02-03 
Location: Richmond, Virginia
Average Post Ranks%:                       
- Post#84692    



Ok this is how I would like to see upgrades happen from now on and will post on the main site as well..

1) Make Back of DB and change the name of the forum folder to something like forum_backup take special note of any modifications they had before

2) copy ALL new files including the ones in the post http://www.fusionbb.com/forum/showtopic.... to the new site under the old forum directory since that way any remenants will not be there

3) copy the old forums config directory into the new forums config directory

4) copy the old forums language files into the new forums /language/XXX directory

5) take one of the new skins doesn't matter which copy it to a new skin call it yoursite and beyond compare that skin to the one they used prior for any differences and update the new skin with the old skins VALUES so they will be in the new skins format.. then copy that new skin into the new forums skin directory

change file permissions to 666 and directories to 777

7) perform update

redo any modifications that need to be done (some wont since they are now features)

if done this way then at the end you should have an old forum you can go back to..

The artist formerly known as scroungr
Couch-Tomatoe
 
Username Topic: 3.1 Files to change
Couchtomatoe
Code Monkey
Total Posts: 3049
*
Birthday: 02-03 
Location: Richmond, Virginia
Average Post Ranks%:                       
- Post#84261    



Heres a few files that need to be changed


cp->fix_forum_counts.php
cp->forumedit.php
cp->sync_data.php
cp->update_forumedit.php
cp->mpp->update_sub_user.php
includes->common.php
includes->user_class.php
mpp->mpp_subscribe.php
docontact.php
editpt.php
listpt.php
newpt.php
recent_activity.php
showblog.php
showgallery.php
showpost.php
showpt.php
showptforreply.php
showtopic.php
showtopicforreply.php




The artist formerly known as scroungr
Couch-Tomatoe


Edited by Couchtomatoe on 08-17-10 05:31 PM. Reason for edit: No reason given.
 
Username Topic: New Skin Elements
Couchtomatoe
Code Monkey
Total Posts: 3049
*
Birthday: 02-03 
Location: Richmond, Virginia
Average Post Ranks%:                       
- Post#82672    



Heres a listing of the 3.0 New Skin Elements to be added to any NON-stock Skin

in stylesheet.css change

Code:

      .post-buttons{         position:relative;         font-size:12px;         padding:6px 10px 6px 5px;         background:none;         margin:0;     }  





to

Code:

      .post-buttons{font-size:12px;         padding:6px 10px 6px 5px;         background:none;         margin:0;     }  





and add

Code:

  #sddm {    margin: 0;     padding: 0;     z-index: 30 } #sddm li {     margin: 0;     padding: 0;     list-style: none;     float: left;     font: bold 11px arial } #sddm li a {     display: block;     margin: 0 1px 0 0;     padding: 2px 2px;     width: 70px;     background: #4C93BF url(theader.gif) repeat-x top;     color: #FFFFFF;     text-align: center;     text-decoration: none } #sddm li a:hover {     background: #F8A22E url(theader-h.gif) repeat-x top; } #sddm div {     position: absolute;     visibility: hidden;     margin: 0;     padding: 0;     background: #EAEBD8;     border: 1px solid #5970B2 } #sddm div a {     position: relative;     display: block;     margin: 0;     padding: 2px 2px;     width: auto;     white-space: nowrap;     text-align: left;     text-decoration: none;     background: #F4F4F4;     color: #6D7A81;     font: 11px arial } #sddm div a:hover {     background: #FF9900 url(theader-h.gif) repeat-x top;     color: #FFFFFF; } .rank_good {     background-image:url(rank_good.gif);     background-repeat:no-repeat; } .rank_bad {     background-image:url(rank_bad.gif);     background-repeat:no-repeat; } .rank_empty {     background-image:url(rank_empty.gif);     background-repeat:no-repeat; } .nobutton {     border: 0px;     padding:0px;     background: transparent;     font-size: 12px;     font-weight:bold;     text-transform:uppercase; } .nobutton:hover {     border: 0px;     background: transparent;     color: #FFFFFF;     cursor: pointer; } .nobutton:active {     border: 0px;     background: transparent;     color: #FFFFFF;     cursor: pointer; }  





also find


Code:

         .comments:link, .comments:visited{background-position0px -420px;}             .comments:hover{background-position0px -420pxtext-decorationunderline;}             .comments span{padding0px 10px 0 0;}  





add below it

Code:

         .moderate_post:link, .moderate_post:visited{background-position0px -481px;}             .moderate_post:hover{background-position0px -481pxtext-decorationnone;}             .moderate_post span{display:none;}         .rate_post:link, .rate_post:visited{background-position0px -511px;}             .rate_post:hover{background-position0px -511px;}             .rate_post span{display:none;}  





...

also need to add some rank graphics to your skin.. you can use these


The artist formerly known as scroungr
Couch-Tomatoe
 
Username Topic: Live FusionBB Sites
Chris Peterson
FusionBB Fanatic
Total Posts: 3758
*
Location: West Fargo, ND
Average Post Ranks%:                       
- Post#82591    



If you are running FusionBB on your live site, please post a request here to have it added to the list!

Please post the title of your site, the link to your forum, and a brief description.
 
Username Topic: Why you cannot search for less than 4 characater strings in MYSQL
Couchtomatoe
Code Monkey
Total Posts: 3049
*
Birthday: 02-03 
Location: Richmond, Virginia
Average Post Ranks%:                       
- Post#81328    



  • Quote:
www.databasejournal.com/features/mysql/a...

Using Fulltext Indexes in MySQL - Part 1
February 3, 2003

One of the more useful MySQL features is the ability to search for text using a FULLTEXT index. Currently this is only available if you use the MyISAM table type (which is the default table type, so if you don't know what table type you're using, it'll most likely be MyISAM). A fulltext index can be created for a TEXT, CHAR or VARCHAR type field, or combination of fields. We're going to create a sample table and use it to explore the various features.

The simple form of usage (the MATCH() function) is available to all MySQL servers from version 3.23.23, while the more complex usage (the IN BOOLEAN MODE modifier) is available from version 4. The first part of this article looks at the former, and the second part at the latter.
A sample table

We're going to use the following table throughout this tutorial.

CREATE TABLE fulltext_sample(copy TEXT,FULLTEXT(copy)) TYPE=MyISAM;

The TYPE=MyISAM clause isn't necessary unless you've set the default table type to be something other than MyISAM (perhaps you use InnoDB tables to make use of MySQL's transactional capabilities). Once you've created the table, populate it with some data, as follows:

INSERT INTO fulltext_sample VALUES
('It appears good from here'),
('The here and the past'),
('Why are we hear'),
('An all-out alert'),
('All you need is love'),
('A good alert');

If you'd already created an existing table, you can add a FULLTEXT index with the ALTER TABLE statement (as well as the CREATE INDEX statement), for example:

ALTER TABLE fulltext_sample ADD FULLTEXT(copy)

Searching for text

The syntax of a FULLTEXT search is simple. You MATCH the field AGAINST the text you are searching for, for example:

mysql> SELECT * FROM fulltext_sample WHERE MATCH(copy) AGAINST('love');
+----------------------+
| copy |
+----------------------+
| All you need is love |
+----------------------+

Searches on a FULLTEXT index are performed case-insensitively (as are searches on TEXT and non-binary VARCHAR fields generally). So the following works as well:

mysql> SELECT * FROM fulltext_sample WHERE MATCH(copy) AGAINST('LOVE');
+----------------------+
| copy |
+----------------------+
| All you need is love |
+----------------------+

FULLTEXT indexes are most often used to search natural language text, such as through newspaper articles, web page contents and so on. For this reason MySQL has added a number of features to assist this kind of searching. MySQL does not index any words less than or equal to 3 characters in length, nor does it index any words that appear in more than 50% of the rows. This means that if your table contains 2 or less rows, a search on a FULLTEXT index will never return anything. In future, MySQL will make this behavior more flexible, but for now it should suit most natural language uses. If most fields in your database contain the word 'music', you probably don't want these records returned, You can use the IN BOOLEAN MODE modifier to get around the 50% threshold, as you'll see in Part 2 of this article.

Results are returned in order of relevance, from highest to lowest.
The main features

A list of the main features of a standard FULLTEXT search follows:

* Excludes partial words
* Excludes words less than 4 characters in length (3 or less)
* Excludes words that appear in more than half the rows (meaning at least 3 rows are required)
* Hyphenated words are treated as two words
* Rows are returned in order of relevance, descending
* Words in the stopword list (common words) are also excluded from the search results. The stopword list is based upon common English words, so if your data is used for a different purpose, you'll probably want to change the list. Unfortunately, doing so at present is not easy. You'll need to edit the file myisam/ft_static.c. recompile MySQL, and rebuild the indexes! To save you hunting through the source, or if you have a binary version of MySQL, here is a list of stopwords. Note that these can and do change with different versions. To be absolutely sure, you'll have to check the specific list for your version.
Stopwords
"a", "a's", "able", "about", "above", "according", "accordingly", "across", "actually", "after", "afterwards", "again", "against", "ain't", "all", "allow", "allows", "almost", "alone", "along", "already", "also", "although", "always", "am", "among", "amongst", "an", "and", "another", "any", "anybody", "anyhow", "anyone", "anything", "anyway", "anyways", "anywhere", "apart", "appear", "appreciate", "appropriate", "are", "aren't", "around", "as", "aside", "ask", "asking", "associated", "at", "available", "away", "awfully", "b", "be", "became", "because", "become", "becomes", "becoming", "been", "before", "beforehand", "behind", "being", "believe", "below", "beside", "besides", "best", "better", "between", "beyond", "both", "brief", "but", "by", "c", "c'mon", "c's", "came", "can", "can't", "cannot", "cant", "cause", "causes", "certain", "certainly", "changes", "clearly", "co", "com", "come", "comes", "concerning", "consequently", "consider", "considering", "contain", "containing", "contains", "corresponding", "could", "couldn't", "course", "currently", "d", "definitely", "described", "despite", "did", "didn't", "different", "do", "does", "doesn't", "doing", "don't", "done", "down", "downwards", "during", "e", "each", "edu", "eg", "eight", "either", "else", "elsewhere", "enough", "entirely", "especially", "et", "etc", "even", "ever", "every", "everybody", "everyone", "everything", "everywhere", "ex", "exactly", "example", "except", "f", "far", "few", "fifth", "first", "five", "followed", "following", "follows", "for", "former", "formerly", "forth", "four", "from", "further", "furthermore", "g", "get", "gets", "getting", "given", "gives", "go", "goes", "going", "gone", "got", "gotten", "greetings", "h", "had", "hadn't", "happens", "hardly", "has", "hasn't", "have", "haven't", "having", "he", "he's", "hello", "help", "hence", "her", "here", "here's", "hereafter", "hereby", "herein", "hereupon", "hers", "herself", "hi", "him", "himself", "his", "hither", "hopefully", "how", "howbeit", "however", "i", "i'd", "i'll", "i'm", "i've", "ie", "if", "ignored", "immediate", "in", "inasmuch", "inc", "indeed", "indicate", "indicated", "indicates", "inner", "insofar", "instead", "into", "inward", "is", "isn't", "it", "it'd", "it'll", "it's", "its", "itself", "j", "just", "k", "keep", "keeps", "kept", "know", "knows", "known", "l", "last", "lately", "later", "latter", "latterly", "least", "less", "lest", "let", "let's", "like", "liked", "likely", "little", "look", "looking", "looks", "ltd", "m", "mainly", "many", "may", "maybe", "me", "mean", "meanwhile", "merely", "might", "more", "moreover", "most", "mostly", "much", "must", "my", "myself", "n", "name", "namely", "nd", "near", "nearly", "necessary", "need", "needs", "neither", "never", "nevertheless", "new", "next", "nine", "no", "nobody", "non", "none", "noone", "nor", "normally", "not", "nothing", "novel", "now", "nowhere", "o", "obviously", "of", "off", "often", "oh", "ok", "okay", "old", "on", "once", "one", "ones", "only", "onto", "or", "other", "others", "otherwise", "ought", "our", "ours", "ourselves", "out", "outside", "over", "overall", "own", "p", "particular", "particularly", "per", "perhaps", "placed", "please", "plus", "possible", "presumably", "probably", "provides", "q", "que", "quite", "qv", "r", "rather", "rd", "re", "really", "reasonably", "regarding", "regardless", "regards", "relatively", "respectively", "right", "s", "said", "same", "saw", "say", "saying", "says", "second", "secondly", "see", "seeing", "seem", "seemed", "seeming", "seems", "seen", "self", "selves", "sensible", "sent", "serious", "seriously", "seven", "several", "shall", "she", "should", "shouldn't", "since", "six", "so", "some", "somebody", "somehow", "someone", "something", "sometime", "sometimes", "somewhat", "somewhere", "soon", "sorry", "specified", "specify", "specifying", "still", "sub", "such", "sup", "sure", "t", "t's", "take", "taken", "tell", "tends", "th", "than", "thank", "thanks", "thanx", "that", "that's", "thats", "the", "their", "theirs", "them", "themselves", "then", "thence", "there", "there's", "thereafter", "thereby", "therefore", "therein", "theres", "thereupon", "these", "they", "they'd", "they'll", "they're", "they've", "think", "third", "this", "thorough", "thoroughly", "those", "though", "three", "through", "throughout", "thru", "thus", "to", "together", "too", "took", "toward", "towards", "tried", "tries", "truly", "try", "trying", "twice", "two", "u", "un", "under", "unfortunately", "unless", "unlikely", "until", "unto", "up", "upon", "us", "use", "used", "useful", "uses", "using", "usually", "v", "value", "various", "very", "via", "viz", "vs", "w", "want", "wants", "was", "wasn't", "way", "we", "we'd", "we'll", "we're", "we've", "welcome", "well", "went", "were", "weren't", "what", "what's", "whatever", "when", "whence", "whenever", "where", "where's", "whereafter", "whereas", "whereby", "wherein", "whereupon", "wherever", "whether", "which", "while", "whither", "who", "who's", "whoever", "whole", "whom", "whose", "why", "will", "willing", "wish", "with", "within", "without", "won't", "wonder", "would", "would", "wouldn't", "x", "y", "yes", "yet", "you", "you'd", "you'll", "you're", "you've", "your", "yours", "yourself", "yourselves", "z", "zero",



Let's have a look at some of the consequences of this. If you were a bit lazy in your typing, and tried 'to look for the word 'love', as follows:

mysql> SELECT * FROM fulltext_sample WHERE MATCH(copy) AGAINST('lov');
Empty set (0.00 sec)

you'd get nothing back, as the FULLTEXT index only contains complete words, not partial words. You'd have to write the full word to get anything back, as you did in the first example.

As mentioned, hyphenated words are also excluded from the FULLTEXT index (they are indexed as separate words), so the following also returns nothing:

mysql> SELECT * FROM fulltext_sample WHERE MATCH(copy) AGAINST('all-out');
Empty set (0.00 sec)

Unfortunately, both words are less than the required 4 letters, so they don't appear on their own either, and cannot be found at all with an ordinary search. Part 2 of this tutorial looks at BOOLEAN MODE searches when you can search for partial or hyphenated words.

You can also search for more than one word at a time, by separating the words with commas. Try and return records containing the words 'here' and 'appears', as follows:

mysql> SELECT * FROM fulltext_sample WHERE MATCH(copy) AGAINST('here');
Empty set (0.01 sec)

Unexpectedly this returns nothing. But, a more careful look at the stopword list shows this word is listed, so they are excluded from the index. Stopwords are a common cause of people complaining that the MySQL FULLTEXT index facility is not working properly. If your query does return a result, then the stopword list in your version of MySQL does not contain the word 'here'.
Relevance

The following example shows how the records are returned in order of precedence:

mysql> SELECT * FROM fulltext_sample WHERE MATCH(copy) AGAINST('good,alert');
+---------------------------+
| copy |
+---------------------------+
| A good alert |
| It appears good from here |
| An all-out alert |
+---------------------------+

The record 'A good alert' appears first, as it contains both words being searched for. You don't have to believe me - just ask MySQL to display the precedence in the results. Simply repeat the MATCH() function in the field list, as follows:

mysql> SELECT copy,MATCH(copy) AGAINST('good,alert') AS relevance
FROM fulltext_sample WHERE MATCH(copy) AGAINST('good,alert');
+---------------------------+------------------+
| copy | relevance |
+---------------------------+------------------+
| A good alert | 1.3551264824316 |
| An all-out alert | 0.68526663197496 |
| It appears good from hear | 0.67003110026735 |
+---------------------------+------------------+

The relevance calculation is fairly complex and is based upon the number of words in the index, the number of unique words in that row, the total number of words in both the index and the result, as well as the weight of the word (for the average English sentence, the word 'cool' will be weighted less, and therefore have a lower relevance, than the word 'dandy', though trends can change!). The figures may differ in your version of MySQL, as MySQL does occasionally tweak the calculation algorithms.

While the standard FULLTEXT search is fairly useful and sufficient for many, MySQL 4 takes it much further. Part 2 of this article looks at BOOLEAN FULLTEXT searches, which offer a lot more functionality.

Using Fulltext Indexes in MySQL - Part 2, Boolean searches
By Ian Gilfillan

Part 1 of this article looked at the fulltext index, and how to search on it using an ordinary MATCH() AGAINST(). Even more powerful, (although only available on the newer MySQL version 4), is the ability to do a boolean search. Part 2 of this article examines the possibilities.

You'll use the same table you used in Part 1. The full list of records is:

mysql> SELECT * FROM fulltext_sample;
+---------------------------+
| copy |
+---------------------------+
| It appears good from here |
| The here and the past |
| Why are we here |
| An all-out alert |
| All you need is love |
| A good alert |
+---------------------------+

To perform a boolean search, the IN BOOLEAN MODE modifier is used. The following query demonstrates the new syntax.

mysql> SELECT * FROM fulltext_sample
WHERE MATCH (copy) AGAINST ('love' IN BOOLEAN MODE);
+----------------------+
| copy |
+----------------------+
| All you need is love |
+----------------------+

An important difference between ordinary MATCH() AGAINST() queries and IN BOOLEAN MODE searches is that the latter does not apply the 50% limit (so the word can appear in more than half the rows).

There are a number of special operators you'll need to know in order to make the most of the boolean search. If no symbol is specified, the appearance of this word causes the relevance of the row to be higher, similar to an ordinary MATCH() AGAINST().
Boolean Search Operators
+ The word is mandatory in all rows returned.
- The word cannot appear in any row returned.
< The word that follows has a lower relevance than other words, although rows containing it will still match
> The word that follows has a higher relevance than other words.
() Used to group words into subexpressions.
~ The word following contributes negatively to the relevance of the row (which is different to the '-' operator, which specifically excludes the word, or the '<' operator, which still causes the word to contribute positively to the relevance of the row.
* The wildcard, indicating zero or more characters. It can only appear at the end of a word.
" Anything enclosed in the double quotes is taken as a whole (so you can match phrases, for example).
Examples
Let's see some of this action. The first example returns all rows containing the word 'here', but not the word 'past'.

mysql> SELECT copy FROM fulltext_sample WHERE MATCH(copy)
AGAINST ('+here -past' IN BOOLEAN MODE);
+---------------------------+
| copy |
+---------------------------+
| It appears good from here |
| Why are we here |
+---------------------------+

Compare the difference between the next two examples:

mysql> SELECT copy FROM fulltext_sample WHERE MATCH(copy)
AGAINST ('here past' IN BOOLEAN MODE);
+---------------------------+
| copy |
+---------------------------+
| It appears good from here |
| The here and the past |
| Why are we here |
+---------------------------+

mysql> SELECT copy FROM fulltext_sample WHERE MATCH(copy)
AGAINST ('here +past'IN BOOLEAN MODE);
+-----------------------+
| copy |
+-----------------------+
| The here and the past |
+-----------------------+

The first works in a similar way to an ordinary MATCH() AGAINST(), albeit without the 50% threshold. The word 'past' is mandatory in the second search (by default a word is optional), so the other two records are not returned.

The next example demonstrates a common mistake.

mysql> SELECT copy FROM fulltext_sample
WHERE MATCH(copy) AGAINST ('+are here' IN BOOLEAN MODE);
+---------------------------+
| copy |
+---------------------------+
| It appears good from here |
| The here and the past |
| Why are we here |
+---------------------------+

The results may appear surprising compared the previous example, but since 'are' contains three or less letters, it is excluded for purposes of the search and is not mandatory.

The next two examples demonstrate a powerful enhancement for searching purposes:

mysql> SELECT copy FROM fulltext_sample
WHERE MATCH(copy) AGAINST ('aler' IN BOOLEAN MODE);
Empty set (0.01 sec)

mysql> SELECT copy FROM fulltext_sample
WHERE MATCH(copy) AGAINST ('aler*' IN BOOLEAN MODE);
+------------------+
| copy |
+------------------+
| An all-out alert |
| A good alert |
+------------------+

By default only whole words are matched, unless the '*' operator is used.

The '<' and '>' symbols are less commonly used, but they allow a great degree of control for relevance. In the following examples, we return the relevance indicator to demonstrate the difference between the queries.

mysql> SELECT copy, MATCH(copy)
AGAINST ('appears good alert' IN BOOLEAN MODE)
AS m FROM fulltext_sample WHERE MATCH(copy)
AGAINST ('appears good alert' IN BOOLEAN MODE);
+---------------------------+------+
| copy | m |
+---------------------------+------+
| It appears good from here | 2 |
| An all-out alert | 1 |
| A good alert | 2 |
+---------------------------+------+

mysql> SELECT copy, MATCH(copy)
AGAINST ('appears <good alert' IN BOOLEAN MODE)
AS m FROM fulltext_sample WHERE MATCH(copy)
AGAINST ('appears <good alert' IN BOOLEAN MODE);
+---------------------------+------------------+
| copy | m |
+---------------------------+------------------+
| It appears good from here | 1.6666667461395 |
| An all-out alert | 1 |
| A good alert | 1.6666667461395 |
+---------------------------+------------------+

The '<' operator decreases the relevance of the word 'good', in this case by approximately 0.33.

mysql> SELECT copy, MATCH(copy)
AGAINST ('appears good >alert' IN BOOLEAN MODE)
AS m FROM fulltext_sample WHERE MATCH(copy)
AGAINST ('appears good >alert' IN BOOLEAN MODE);
+---------------------------+------+
| copy | m |
+---------------------------+------+
| It appears good from here | 2 |
| An all-out alert | 1.5 |
| A good alert | 2.5 |
+---------------------------+------+

The '>' operator increases the relevance of the word 'alert', in this case by 0.5.

The parentheses group words into a subexpression. In the following example, the '+' symbol applies to the group of words, so that at least one of 'appears' or 'past' must appear.

mysql> SELECT copy, MATCH(copy)
AGAINST ('+(appears past)' IN BOOLEAN MODE)
AS m FROM fulltext_sample WHERE MATCH(copy)
AGAINST ('(appears past)' IN BOOLEAN MODE);
+---------------------------+------+
| copy | m |
+---------------------------+------+
| It appears good from here | 1 |
| The here and the past | 1 |
+---------------------------+------+

You can also apply the operators to words in the subexpression, as follows:

mysql> SELECT copy, MATCH(copy)
AGAINST ('+(>appears <past)' IN BOOLEAN MODE)
AS m FROM fulltext_sample WHERE MATCH(copy)
AGAINST ('+(>appears <past)' IN BOOLEAN MODE);
+---------------------------+------------------+
| copy | m |
+---------------------------+------------------+
| It appears good from here | 1.5 |
| The here and the past | 0.66666668653488 |
+---------------------------+------------------+

The '~' operator contributes negatively to the relevance, but does not bar the word from appearing, as the '-' operator does. It also does not do the same as the '<' operator, which is to make a reduced, yet still positive, difference to the relevance. These subtle difference allows for powerfully tuned searches, but can cause confusion. Look at the difference between the following. First, the word 'here' is compulsory, and the word 'past' optional:

mysql> SELECT copy, MATCH(copy)
AGAINST ('+here past' IN BOOLEAN MODE)
AS m FROM fulltext_sample WHERE MATCH(copy)
AGAINST ('+here past' IN BOOLEAN MODE);
+---------------------------+-----------------+
| copy | m |
+---------------------------+-----------------+
| It appears good from here | 1 |
| The here and the past | 1.3333333730698 |
| Why are we here | 1 |
+---------------------------+-----------------+

Next, a reduced relevance for the word 'past'. The same results are returned, but the record with both words ('The here and the past') has less weighting, though still more than the other records.

mysql> SELECT copy, MATCH(copy)
AGAINST ('+here <past' IN BOOLEAN MODE)
AS m FROM fulltext_sample WHERE MATCH(copy)
AGAINST ('+here <past' IN BOOLEAN MODE);
+---------------------------+-----------------+
| copy | m |
+---------------------------+-----------------+
| It appears good from here | 1 |
| The here and the past | 1.2222222089767 |
| Why are we here | 1 |
+---------------------------+-----------------+

Take note of the relevance in the next example:

mysql> SELECT copy, MATCH(copy)
AGAINST ('+here ~past' IN BOOLEAN MODE)
AS m FROM fulltext_sample WHERE MATCH(copy)
AGAINST ('+here ~past' IN BOOLEAN MODE);
+---------------------------+------------------+
| copy | m |
+---------------------------+------------------+
| It appears good from here | 1 |
| The here and the past | 0.83333331346512 |
| Why are we here | 1 |
+---------------------------+------------------+

The important difference is that the relevance is negatively affected, and is now lower than the other two records. This means if you asked for only '~past', you'd get nothing back, as the relevance would be lower than 0 (and therefore not returned)

mysql> SELECT copy, MATCH(copy)
AGAINST ('~past' IN BOOLEAN MODE)
AS m FROM fulltext_sample WHERE MATCH(copy)
AGAINST ('~past' IN BOOLEAN MODE);
Empty set (0.00 sec)

Finally, '-' simply removes the second record from the result set, as we've seen before.

mysql> SELECT copy, MATCH(copy)
AGAINST ('+here -past' IN BOOLEAN MODE)
AS m FROM fulltext_sample WHERE MATCH(copy)
AGAINST ('+here -past' IN BOOLEAN MODE);
+---------------------------+------+
| copy | m |
+---------------------------+------+
| It appears good from here | 1 |
| Why are we here | 1 |
+---------------------------+------+

The final operator, the double quotes ("), is useful to group phrases together. So, if you were interested in returning 'good from here' but none of those words if they did not appear in the phrase, you'd use:

mysql> SELECT copy, MATCH(copy)
AGAINST ('"good from here"' IN BOOLEAN MODE)
AS m FROM fulltext_sample WHERE MATCH(copy)
AGAINST ('"good from here"' IN BOOLEAN MODE);
+---------------------------+------+
| copy | m |
+---------------------------+------+
| It appears good from here | 1 |
+---------------------------+------+

For many applications, boolean searches are one of MySQL 4's most useful features. With careful use, you can save yourself substantial of development time, and add many useful enhancements. Good luck!





So as you see its NOT a limitation of Fusion or Any Software other than a limitation in MYSQL itself.

as mentioned one simple way would be to add a google search box to the site which would basically send a command to google as such.. searching for the word 'cry'

cry site:http://www.fusionbb.com
The artist formerly known as scroungr
Couch-Tomatoe


Edited by Couchtomatoe on 05-15-09 01:57 PM. Reason for edit: No reason given.
 
Username Topic: [IN QUEUE] Templates: Template Editor
Lori
FusionBB Documentation Goddess
Total Posts: 2683
*
Birthday: 10-02 
Location: Junction City, Kansas
Average Post Ranks%:                       
- Post#78175    



Need to add:

*path

*need more info on the second dropdown box ('cp')

*ditto on the Copy template option (far right)

*any other blah blah that's needed




















Edited by Lori on 12-29-08 01:49 PM. Reason for edit: No reason given.
 
Username Topic: [IN QUEUE] Post/Poster Ranking
Lori
FusionBB Documentation Goddess
Total Posts: 2683
*
Birthday: 10-02 
Location: Junction City, Kansas
Average Post Ranks%:                       
- Post#78145    



CTs changelog post about it--with pics


*add details on how to do each

*admin and others may have it set that they have to approve your ranking before it will become official



Edited by Lori on 12-29-08 01:54 PM. Reason for edit: No reason given.
 
Username Topic: [IN QUEUE] Skins: Skin Editor
Lori
FusionBB Documentation Goddess
Total Posts: 2683
*
Birthday: 10-02 
Location: Junction City, Kansas
Average Post Ranks%:                       
- Post#78141    



Super cool facts about this topic:

*new to 3.0

*include images

*include paths

***Put links to and from this topic--or just leave 'as is'--it will list out right below the current topic. Or do both



Edited by Lori on 12-29-08 01:54 PM. Reason for edit: No reason given.
 
Username Topic: [FUTURE ADDITION TO CALENDAR TOPICS] Personal Calendars
Lori
FusionBB Documentation Goddess
Total Posts: 2683
*
Birthday: 10-02 
Location: Junction City, Kansas
Average Post Ranks%:                       
- Post#78139    



For this topic:

*info should be added to the Admin and User Calendar topics

*Images as needed

*Path to or how to get there

*How to work with--if different from regular calendar. If it's the same, then reference that fact



**Edit** Since there is NO Admin Calendar topic--need to add (or copy) the User one to the Admin section (?) as well as do the above....

Edited by Lori on 12-29-08 01:50 PM. Reason for edit: No reason given.
 
Username Topic: [IN PROCESS] Passwords: Resetting
Lori
FusionBB Documentation Goddess
Total Posts: 2683
*
Birthday: 10-02 
Location: Junction City, Kansas
Average Post Ranks%:                       
- Post#78138    



What is needed for this wonderful topic:

*This is a 3.0 and newer topic

*Images of the password-resetting area of the AdminCP

*Path to the place to do all this fun


CTs changelog posting--with pictures



TO RESET PASSWORD BY LOGIN, EMAIL, or GROUP




AdminCP >> Users >> Reset Passwords

Enter the user login name, email address, or choose the group for whom you want to reset the password(s) then click 'Proceed'.

THEN WHAT?? It isn't working? <I tried it and got a blank screen when chose Admin








AdminCP >> Cron Scheduler >> Manage Cron Tasks

Double Check this info!!This allows you to set up a cron task that will cause passwords to be reset on a schedule that you choose. (Put examples here)

Edited by Lori on 12-29-08 01:48 PM. Reason for edit: No reason given.
 
Username Topic: [IN QUEUE] Link attachments to a PT /Poster
Lori
FusionBB Documentation Goddess
Total Posts: 2683
*
Birthday: 10-02 
Location: Junction City, Kansas
Average Post Ranks%:                       
- Post#78137    



What is needed....


*Version (perhaps put 'applies to all' & if someone grumbles that it doesn't work with 'version blah blah', send them off to peel potatoes? )

*This topic includes a MySQL query language dealie--so will probably need to enclose the aforesaid language in a [ code ] so that everything doesn't go wonky...

***Perhaps add this to the Admin topic on PTs (if there is one) or to the Admin topic on attachments (ditto)--or put somewhere....

Edited by Lori on 12-29-08 01:53 PM. Reason for edit: No reason given.
 
Username Topic: Need Even More Customizations? FusionBB Dev is THE Place to Go!
Lori
FusionBB Documentation Goddess
Total Posts: 2683
*
Birthday: 10-02 
Location: Junction City, Kansas
Average Post Ranks%:                       
- Post#77981    



Want to go beyond the topics we have here?
Need a special customization just for
your site?




If you're looking for mods for your FusionBB-based messageboard, FusionBB Dev is the place to go!

FusionBB Dev is the official home for hacking/modifications and addons for FusionBB.com. Unlike other forum developers, FusionBB Dev isn't a third-party site, it's operated by the FusionBB developers themselves.

(Why? Because we're all big ol' hackers at heart. )


Check Us Out!







Edited by Lori on 07-14-08 02:39 PM. Reason for edit: No reason given.
 
Username Topic: Helpful Show Status Descriptions
Couchtomatoe
Code Monkey
Total Posts: 3049
*
Birthday: 02-03 
Location: Richmond, Virginia
Average Post Ranks%:                       
- Post#77888    



  • Quote:
Open_tables, Opened_tables

This statistic shows you the number of tables currently open, while the Opened_tables variables shows the number of tables opened since the server was last restarted. These values provide a good indication of whether your table cache is of the right size; a high value for Opened_tables indicates that your cache should be larger.

Slow_queries

This statistic indicates the number of queries that have taken longer than a predefined per-query time limit. A large value here indicates that the server is not able to process queries at the speed it should and is a cause for concern (although you should make this determination after checking the slow query log, which contains the actual query strings, to see if it's the queries themselves that are unusually long or complex).

Select_scan


This statistic shows the number of joins which required a full scan of the first table named in the join. Since a full table scan is time- and resource-intensive, a high value here means that your queries are operating inefficiently and perhaps require further optimization.

Select_full_join

This statistic reveals the total number of joins performed without making use of indexes. An index speeds up table searches and is advisable on all fields that are queried frequently. Therefore, a high value here means that MySQL is not using indexes and is therefore taking longer to build a result set. The problem can be corrected (or at least mitigated) by indexing important fields of the join.

Qcache_hits


This statistic shows the number of accesses to the new MySQL query cache. The query cache stores the results of frequently-used queries so as to speed up response time; a high value here means that MySQL is working efficiently by using the cache instead of rebuilding result sets every time the same query is fired.

The artist formerly known as scroungr
Couch-Tomatoe


Edited by Couchtomatoe on 07-09-08 08:39 AM. Reason for edit: No reason given.
 
Username Topic: Tips for Keeping Your FusionBB Site Secure
Lori
FusionBB Documentation Goddess
Total Posts: 2683
*
Birthday: 10-02 
Location: Junction City, Kansas
Average Post Ranks%:                       
- Post#77718    



(Applies to all versions of FusionBB)

Listed below are some things you can do to increase the level of security for your forums:



1. Always upgrade to the latest stable version.

2. Password protect your fusion/cp directory using .htaccess /.htpassword.
Link to a 'How To' article on the javascriptkit.com website.

3. Make sure the fusion/install directory is NOWHERE on your website after you upgrade or install.

4. Make sure all the Admin and Mod passwords are secure.
Change them if you have any doubts. And use hard to guess passwords.

5. Make sure ONLY TRUSTED MEMBERS can do following. Limiting access to these helps prevent file-type change hacking.

In Forums Permissions:

* Can Use HTML in Posts
* Can Attach Files to Posts
* Can Attach Multiple Files to Posts
* Can Use Lightbox


In Control Panel Permissions:

* Can Manage Images


In Site Permissions:

* Can Use uploaded avatars
* Can Attach Files to Private Topics
* Can Attach Multiple Files to Private Topics


6. NEVER allow HTML in posts, PMs or in sigs.

7. If you have phpMyAdmin make sure it's password protected.

8. If you suspect a hacking attempt, ask your host to change the login password for your web account.

9. Make absolutely sure there are no viruses, trojans or keylogger spyware on your PC.
Any of these could steal your password and other personal info.

10. Use a different password for each forum you sign up with.
Use a different password for your forum as you do for the .htaccess directory password.




Please Note!!
Your forums are only as secure as the passwords you use and the server it is on. If the server is accessed then there's nothing Fusion can do to prevent potential security violations.







(Thanks to resident Code Monkey, CT, for this important information!)


Edited by Lori on 07-25-08 08:39 PM. Reason for edit: No reason given.
 
Username Topic: [FUTURE TOPIC] My Userpage/Blog Stuff **Partially waiting on info**
Lori
FusionBB Documentation Goddess
Total Posts: 2683
*
Birthday: 10-02 
Location: Junction City, Kansas
Average Post Ranks%:                       
- Post#77601    



To include:

*How to use
*Adding/removing a buddy
*Control Panel buddy list option (auto add/not)
*Any Admin-related functions/controls/settings/blah blah blah
*etc etc etc



Sing together now: the POSTS get ranked on the Show Topics page & the POSTERS get ranked on their user's blog and the user's Show User page.


*******This topic may need to be split or??: part going to the Admin section and part going into the User section***********






User page top: Profile-Wall-Gallery


User page bottom: Bio-Blog-Friends


Edited by Lori on 12-29-08 01:51 PM. Reason for edit: No reason given.
 
Username Topic: Secure Passwords
VertexBilly
FusionBB Addict
Total Posts: 875
*
Location: Las Vegas, NV
Average Post Ranks%:                       
- Post#76798    



Couch mentioned about secure passwords as one step to securing FusionBB.

Over at VertexHost I have a lot of users that tell me they are using secure passwords and then I find out the password is something like "Fluffy07".

So I thought I would post a quick topic here with some info that can help you create easy to remember yet secure passwords.

Passwords should:
  • not contain dictionary words or proper names
  • Use both upper and lower case letters
  • use both letters and numbers
  • should be at least 6 characters long


One easy to use method that I recommend for creating passwords that are both secure and easy to remember is to write a short sentence that consists of proper nouns as well as numbers (or words that can be replaced with numbers like "for") and then take the first letter of each word and use that as a password.

An example would be:
"My dog Tess is 5 and my cats are 7."

This is can convert to the following secure password that is easy to remember for me:
MdTi5amca7

Not only is it easy to remember but Microsoft verifies this is a Strong password:

http://www.microsoft.com/protect/yoursel...

Remember secure passwords don't have to be hard and please do use them. All other security measures are wasted if your admin or hosting password is "password" or something equally simple.

Change your passwords. Most people have let someone else use their password at some point in time so try and get in the habit of changing them every 3 - 6 months.

Lastly there are some great tools for helping you keep track of your passwords. I personally recommend KeePass .

Billy Cooter
Managing Partner, VertexHost.com
 
  Results: 1 - 20 of 39  Today the 24th Apr 2014 | Yesterday        Days   Weeks
Calendar
SMTWTFS
 12345
6789101112
13141516171819
20212223242526
27282930 
Current Quote
"Well, this is different, but nice. I see there are many, many new features. The color choices are good, Instrutions are good, the smilies seem very animated and friendly."
~ CallieAnn
FusionBB™ Version 3.2 | ©2003-2014 InteractivePHP, Inc.
Execution time: 0.242 seconds.   Total Queries: 296   Zlib Compression is on.
All times are (GMT-4). Current time is 04:09 AM
Top