By walden on

Has any one seen any examples of a drupal forum with top notch design? I'm looking for an example of what's possible in terms of visual styling and usability. I want to create something of adobe or apple caliber.

Thanks!

Comments

jhuckabee’s picture

jhuckabee commented

I ran into these links on Drupal a while back. They should be helpful for you.

This post is all about good looking forums. I also found this one that I thought looked really cool.

Good luck,
Josh

BoitumeloB’s picture

BoitumeloB commented

WAMP server turn Orange while online.Apache has started but Mysql does not start. Find attached Mysql log for assistance.
2015-01-29 08:44:10 7932 [Note] InnoDB: Completed initialization of buffer pool
2015-01-29 08:44:11 7932 [Note] InnoDB: Highest supported file format is Barracuda.
2015-01-29 08:44:11 7932 [Note] InnoDB: The log sequence numbers 469462267 and 469462267 in ibdata files do not match the log sequence number 1201992171 in the ib_logfiles!
2015-01-29 08:44:11 7932 [Note] InnoDB: Database was not shutdown normally!
2015-01-29 08:44:11 7932 [Note] InnoDB: Starting crash recovery.
2015-01-29 08:44:11 7932 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-01-29 08:44:11 7932 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace premier/xmlsitemap_sitemap uses space ID: 323 at filepath: .\premier\xmlsitemap_sitemap.ibd. Cannot open tablespace premier1/cache_field which uses space ID: 323 at filepath: .\premier1\cache_field.ibd
InnoDB: Error: could not open single-table tablespace file .\premier1\cache_field.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.