Dear beautiful members,

We are very pleased to release a new update for the version 3. It's echoPHP MF 3.0.0 RC3. It includes bug fixes and updates for the version 3.0.0 RC2. This release also includes new features.

WHAT'S CHANGED?
fixed: clients can't un-publish an article or can't update an article.
fixed: change forum name improperly in some cases.
fixed: 'MF admin area -> Manage Categories' doesn't allow category description blank.
fixed: MF can't detect phpBB version.
fixed: 'MF admin area -> Prune Inactive Forums' doesn't work properly.
fixed: /mf_admin/cron.php doesn't work for cron on some servers.
fixed: phpBB Session ID isn't removed correctly.
fixed: MF doesn't apply all settings changed by forum administrators to parked domains.
fixed: alert 'Admin has been taken successfully!' twice.
fixed: 'MF admin area -> Upgrades', can't change product type.
fixed: MF admin area -> Manage Ads, 'Ads between posts' editor shows 'Top Ads'.
fixed: MF fetch wrong template of MF admin area and MF pages.
fixed: PayPal gateway doesn't accept e-check payment.
fixed: lose product name of orders when delete a product.
fixed: forum table prefix is not updated when forum name/domain changed.
fixed: 'Wrong Number Entered' message in MF admin -> login page at the first visit.
fixed: XSS bug on signup and upgrade page.
fixed: board backup from Admin Area of large forum return 0KB.
fixed: get error file /admin/mf_backup_db.php not found when access to /admin/admin_db_utilities.php (only on phpBB2 MF)
new: supports multiple styles.
new: MF admin area -> Manage Styles and Manage Templates, new features to manage styles and templates via MF admin area.
new: ability to backup all forums or entire system using cron or your browser.
new: MF admin area -> Manage Backups, new feature allows you delete, download, restore multiple forum backups.
new: MF admin area -> Upload a backup, new feature allows you upload and restore a single forum backup.
new: MF admin area -> Maintain Databases, new feature allows you repair/check/optimize databases.
new: ability to pull lastest news for home page, directory, etc.
new: new option to disallow 'FROM' header in emails.
new: new option to disable UTF-8 in email subject.
new: new option to turn off board_directory.php
new: ability to view forum table prefix.
new: ability to set default homepage style.
new: ability to set default homepage language.
new: ability to switch to another languages on homepage.
new: ability to set default domain for signup page.
new: ability to set default category for signup page.
new: MF admin area -> Utilities, add new utility 'Empty Backup Folder', allows you delete all backups with a click (only authorized admins can see and do it).
new: MF admin area -> Utilities, add new utility 'Run Backup', allows you backup your forums or entire system on your browser.
new: MF admin area -> Utilities, add new utility 'Sys. Backups Download', allows you download system backups.
new: 2 new phrases added: directory_turned_off, lastest_news.
update: supports phpBB 3.0.2
update: new .htaccess in /logos to prevent access to non-image files, such as: .php, .html files.
update: MF admin area -> News, save create time and update time for news.
update: board_directory.php hide empty category description.
update: embed langauge select box into signup template instead of assigning it to $language_select variable to allow clients customize it easier.
update: remove entire /mf_data/mf_templates
update: ability to preview inactive forums before pruning.
update: MF admin area -> Maintenance is changed to Utilities.
update: MF admin area -> Utilities, 'Clear Cached Files' now replace 'Cear User Forums Cached Files' and 'Clear MF Cached Files'.
update: MF admin area -> Cron Jobs, add new options to control backup behavour for cron.


UPGRADE INSTRUCTIONS:
Please refer to README.html in the upgrade package (echoPHP MF 3.0.0.RC2 - Upgrade to 3.0.0.RC3.zip).


INSTALLATION INSTRUCTIONS:
Please refer to README.txt in the installation package (echoPHP phpBB MultiForums v3.0.0.RC3.zip).

VERSION COMPATIBILITY:
Before upgrading/installing your MF, check your server configuration for new version compatibility. Click here to download MF detector. If your server isn't affordable to upgrade to or install this new version, upgrade your server then run the detector again.

We encourage all clients upgrade their echoPHP MFs to the lastest version as soon as possible to get bug fixed and new updates/features.

If you have any questions/problems, please do not hesitate to contact us at our helpdesk (http://help.echophp.com) at anytime.

Thank you.

Wow, I like the new features. It looks really great.

Thank you for this new version:)

I can't find it ? I can find the readme.html but there are no upgrade instructions?

Make sure you downloaded the UPGRADE, not the fresh install.
The UPGRADE does have it, I just went through it with mine.


Yeah, it's 'great', but it does not follow proper programming protocols.
RC means the thing is FEATURE LOCKED, done, finit, completed. The only stuff to be 'added' to the code is a bug fix here or there. Otherwise, this is 'beta' software.

We've already been through two changes in the template structure with v3, and we haven't even seen a stable version of this software out there. Come on people, make up your minds, stop trying to create your own standards. Coding standards are there for a reason.

As far as the 'release':
The 'backups' are NOT necessary, yet, lo and behold can we disable the 'daily' option? Of course not. So, we're stuck either not running cron (bad idea, because it DOES put out useful things), or dealing with backups that we don't need.

The only time that 'backups' are necessary are when you don't do proper system backups. The way backups are done here is a disgrace, and KILLS even a quad core server. Come on now, wake up, STOP forcing individuals to do backups every time the cron is run! Come on now, allow individuals to run THEIR OWN backups, instead of forcing your own system loaded backups down our throat!

Please, adhere to proper coding standards and practices, stop putting 'new features' into what should be a feature locked distribution, get it out the door as stable, and THEN start working on features for the next version. This is the PROPER way to do things. You can't just dictate your own standards here.

Daily backups can be disabled.

The readme txt states that it's optional to update wrapper.html and at the last step it says to delete this file, why?
My website is perfectly integrated with the main template files in mf_temp.
If i delete wrapper.html is there a new way to customize the look of echophpmf?
Is it even worth the upgrade?
Also it states that it will place all template html files into the database,
Won't this make databases gy-normous and hard to move or even edit the templates for mods?

I'd like the opinion of staff as well as other mf clients, espeacially ones that have been here awhile.....is it worth it?

The upgrade places all templates into database to help you manage templates easier, without using FTP . It also implements multiple styles for domains. You now can offer a free forum hosting service on domains have separate styles and languages.

In your case, after the upgrade, you may not need to update templates if you don't have time. But new features won't work for you, such as: Language switcher, Default Category, Default Domain Name, etc.

And what about the wrapper.html, and being able to ntergrate your website?

I understand moving the templates into the database but that still makes the database huge.
Very hard for moving, and if you forum service has 100,000 plus per server, having a cluttered database isn't good.
Well at least not for me.
Perhaps i can find away to customize the upgrade.

I dont think you understand, not the forum templates are being set in the database, but the template of the homepage..

That won't cost much database space..

You mean the template of the mf script or the index page of every forum template?
Because the upgrade states "This upgrade will import all templates (all .html files found) in /mf_temp into database to allow you manage templates easier via MF admin area. So all .html files in /mf_temp will no longer be needed, you can delete them to free some disk space after the upgrade."

So How do I not understand?
This means all the template files in the entire folder will now be fused with the database, which is not good.
What if i have to extract the images and template files from the database to move it to a new server.
Ever tried to move a 600GB database before? Not easy.
And with all that extra clutter it will take even longer.
And what about customizing the look of the mf script.
I already have it intergraded smoothly.
Will it be as easy to open, copy, and edit the file to customize?
What about future releases, will there be another drastic change that will rearrange everything and the way we have it set up?

What i'm getting at is why not have these features optional?
Be able to get and use the upgrade but not use some of the features like the database and the template files.

Another thing is the mods.
I'm useing all 22 mods and it's a pain in the a$$ everytime ther's a new upgrade to have to redo all the mods for every template.
That's 300 more modifications i have to do.
I like this mf script but i like it alot better when Jen used to own and run it.

isnt it just the template for phpbbMF site that gets moved to db? Not the forum templates.

Yeah, it says all the template file in the mf_temp folder.
Which is better than the whole styles folder.
However i still don't like it.
Personally i like to keep the database strictly mysql and nothing else.
No images, no files, nothing.
Why? Because there is no quick way to remove them if you decide to change hosts or upgrade server or change to a better mf script.

Anyway still my question about being able to easily, even if you can, continue to customize the front page to integrate with my website.
And also why does the upgrade instructions say that you can edit the wrapper.html (optional), and then the last step says to delete this file because it won't work?

Because accidents happen.