Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • yes, super cache was deactivated, all plugins were for that matter, so i think it must have been another problem.

    Also this bug only appeared when I tried to activate the theme, an other admin had no such problem. The only thing that worked for me was uncommenting this part of the themes.php:

    <?php if ( ! validate_current_theme() ) : ?>

    <div id="message1" class="updated fade"><p><?php _e('The active theme is broken. Reverting to the default theme.'); ?></p></div>

    I’m on 2.9.1.1

    right now i’ve fixed this for me by just disabling the validate_theme function in my themes.php, so it works fine now.

    But this may not be for everyone.

    Oh, sorry about that last post! I was wrong, you musn’t activate this plugin globally.

    The reason I though that you had to was because the tweetstream-settings link doesn’t show up in the buddypress navigation-bar on the top of the page if you are on a wpmu-blog (like http://blog.testbp.org)

    You need to be on the start page to see it.

    @blackphantom

    thanks for the plugin, it works like a charm!

    But what I don’t quite understand: You must activate the plugin site-wide for it to show up in the profile settings of every user, don’t you?

    Now it seems to me like every user has access to the tweetstream settings in the admin area, and can see the api-key and the secret api-key and change them globally too!

    Isn’t that a problem?

    I have the same problem.

    The buddypress default theme is not activateable since I upgraded to Buddypress 1.2, and is still not solved after upgrading to Buddypress 1.2.1.

    I also get the message:

    The active theme is broken. Reverting to the default theme.

    This error message apparently appears if the activated theme has no index.php or style.css

    here is a snippet from the theme-php:

    /**

    * Checks that current theme files ‘index.php’ and ‘style.css’ exists.

    *

    * Does not check the ‘default’ theme. The ‘default’ theme should always exist

    * or should have another theme renamed to that template name and directory

    * path. Will switch theme to default if current theme does not validate.

    * You can use the ‘validate_current_theme’ filter to return FALSE to

    * disable this functionality.

    *

    * @since 1.5.0

    *

    * @return bool

    */

    Our default theme is and should stay K2 for new users, so we can’t change that. But apparently we need an index.php which the buddypress default theme seems not to have.

    Any Ideas?

Viewing 5 replies - 1 through 5 (of 5 total)
Skip to toolbar