Forum Replies Created

Viewing 15 replies - 91 through 105 (of 113 total)
  • Thread Starter Becki Beckmann

    (@becki)

    well, actually figured out that this error had nothing to do with a sidebar widget enabled or not.

    this fatal error shows up once a non-admin user is logging in to the dashboard. other users have reported similar issues:

    http://support.addthis.com/customer/portal/questions/358448

    http://support.addthis.com/customer/portal/questions/362900-last-update-cant-login-users-only-admin

    hope this helps

    cheers
    becki

    Thread Starter Becki Beckmann

    (@becki)

    hi @meetwp,

    yes, i tried domain mapping and it works without any problems.

    but for my special setup described above i would need separate wordpress multisite installs for each TLD to get the language sub-directory structure working.

    it’s not possible to do that with only one wordpress multisite install for 2 or more domains …

    hope that helps

    greetings
    becki

    Thread Starter Becki Beckmann

    (@becki)

    hi brasofilo 😉

    not sure what makes it so hard for you to understand?

    the question simply is -> can i use only one wordpress multisite install to get a sub-directory language structure for 2 or more domain?

    domain.com/en/ … /de/ … /fr/ … etc
    anotherdomain.com/en/ … /de/ … /fr/ … etc …

    or would i need separate wordpress multisite installs, one for each domain, to get this working?

    from the SEO aspect of a website i do prefer languages in sub-directories instead of sub domains. this is the important thing for me.

    so … if you got any further questions, then please ask

    also didn’t get any other reply from the plugin devs and also didn’t do any more research by mysefl on that topic

    hope that helps & all the best

    greetings
    becki

    ok … i totally understand you 😉 don’t get me wrong i made my own experiences with customers … mostly a big big headache 😉

    well … instead of menu creating have a look at this exclude page plugin ->

    http://wordpress.org/extend/plugins/exclude-pages/

    once activated you will get another exclude widget when creating a page / post and you simply mark ‘exclude this page from navigation’ and i think it doesn’t get easier then that 😉

    give it a try!

    on the other site you can also hack into the wordpress core and do a var_dump on the wp_list_menu and unset some vars in the array …

    but give that exclude page thingy a try first

    yes … customers can be very time consuming 😉

    greetings & best of luck
    becki

    did you have a look at the menu option? it’s really easy to use, just a bit drag and drop and you’re done. go & give it a try at least 😉

    why don’t you use the menu option at -> ‘appearance’ -> ‘menu’?
    there you can create a custom menu via drag and drop …

    hi there,

    you could use the navigation menu option under ‘appearance’ -> ‘menu’ and create your custom menu

    or … i used some plugin called exclude pages which also did the trick for me

    perhaps this might help 😉

    Thread Starter Becki Beckmann

    (@becki)

    ok … sorry for actually posting this. had a quick look in the source code and after that it was quite clear how this custom css file for nextgen gallery plugin is working

    it just needs to be in the root on the theme directory and not in an additional folder /nggallery

    /**
    	 * Look for the stylesheet in the theme folder
    	 *
    	 * @return string path to stylesheet
    	 */
    	function get_theme_css_file() {
    
      		// allow other plugins to include a custom stylesheet
    		$stylesheet = apply_filters( 'ngg_load_stylesheet', false );
    
    		if ( $stylesheet !== false )
    			return ( $stylesheet );
    		elseif ( file_exists (STYLESHEETPATH . '/nggallery.css') )
    			return get_stylesheet_directory_uri() . '/nggallery.css';
    		else
    			return false;
    	}

    the constant STYLESHEETPATH is declared via this function

    /**
    	 * Filesystem path to the current active template stylesheet directory
    	 * @since 2.1.0
    	 */
    	define('STYLESHEETPATH', get_stylesheet_directory());

    so … simply put your custom css in the root of your theme and all is fine 😉

    probably this might help someone?

    thanks, and sorry for wasting your time

    greetings
    becki

    Thread Starter Becki Beckmann

    (@becki)

    do you have the web developer firefox extension installed? if not then do so … probably also firebug extension … then you can see the errors and probably trace it back to another plugin or core function

    yes … i can confirm the same issues here on my multi site install. dashboard not working properly and if you debug with web developer firefox extension it will throw 2 jquery errors from the headspace2 plugin

    unfortunately i’m not a big jquery guy so i think we have to be patient and wait for a patch from the headspace2 dev guys

    btw … really thanks for such a great plugin … two thumbs up!

    Thread Starter Becki Beckmann

    (@becki)

    hi there,

    i think i found the problem

    abigailm … are you using the headspace2 plugin?

    i had a deeper look with the web developer toolbar and found 2 jquery errors ->

    Error: jQuery(“#desc_1309987823”).Counter is not a function
    Error: jQuery(“#desc_1309987877”).Counter is not a function

    and these errors are coming from headspace2 plugin

    [Code moderated as per the Forum Rules. Please use the pastebin]

    and i even found a post on the headspace2 plugin page at wordpress where people have similar issues

    http://wordpress.org/support/topic/dashboard-problem-after-32-upgrade?replies=3

    i think that could be the culprit … seems we have to wait for an update from the headspace2 guys

    also if i look in the dashboard i don’t see a headspace2 widget but if i look in the page source i see a headspace2 widget code.

    i think that must be it!

    so … i think we have to applaud ipstenu 😉 it was … probably is … another plugin causing this issue

    more when i find out more …

    Thread Starter Becki Beckmann

    (@becki)

    hi abigailm

    you’re a star 😉

    So it is a big help to offer up suggestions for more debugging — but denying that there is a problem in the face of multiple reports doesn’t make sense.

    after the last reply from user ipstenu, which i actually didn’t find very helpful, i just couldn’t be bothered to send another reply … sorry

    i had the same impression of denying that there is a problem

    so thanks abigailm, i couldn’t have used better words 😉

    aehm …. by the way … i know my name becki is a bit confusing as most people think i’m female … hahaaa 😉 but the female becky is written with a ‘y’ and the male becki is written with an ‘i’, at least here in germany.

    well … i know, very confusing, but i got this nickname assigned by some friends of mine in the last couple of years

    here’s the actual proof being male -> http://beckspaced.com

    thanks again abigailm 😉

    Thread Starter Becki Beckmann

    (@becki)

    probably some other widgets are causing the problem?

    you can disable all widgets if you like. there is this global $wp_meta_boxes which you could have a look at to see which widgets are loaded. there are 2 kinds of widgets ‘normal’ and ‘core’. you could loop with foreach through the normal and core and then remove them one by one to see if removing widgets helps to improve things.

    have a look at the function below i used to figure out things ->

    function removeDashboardWidgets() {
    	// Globalize the metaboxes array, this holds all the widgets for wp-admin
    
    	global $wp_meta_boxes;
    
    	/*
    	foreach (array_keys($wp_meta_boxes['dashboard']['side']['core']) as $name){
    		echo ("<p>");
    		echo ($name);
    		echo("</p>");
    
    	}
    	*/
    
    	// Remove the quickpress widget
    
    	unset($wp_meta_boxes['dashboard']['side']['core']['dashboard_quick_press']);
    
    	// Remove the incomming links widget
    
    	unset($wp_meta_boxes['dashboard']['normal']['core']['dashboard_incoming_links']);
    	unset($wp_meta_boxes['dashboard']['normal']['core']['dashboard_recent_comments']);
    	unset($wp_meta_boxes['dashboard']['normal']['core']['dashboard_plugins']);
    	unset($wp_meta_boxes['dashboard']['side']['core']['dashboard_primary']);
    	unset($wp_meta_boxes['dashboard']['side']['core']['dashboard_secondary']);
    	unset($wp_meta_boxes['dashboard']['side']['core']['dashboard_recent_drafts']);
    } 
    
    // Hoook into the 'wp_dashboard_setup' action to register our function
    
    add_action('wp_dashboard_setup', 'removeDashboardWidgets' );

    a var_dump($wp_meta_boxes) will probably also give you the info you need

    best of luck and please post your report here

    Thread Starter Becki Beckmann

    (@becki)

    yep … great … we got another one 😉 who can confirm that it has nothing to do with plugins or the different browsers

    abigailm … just put that piece of code into your functions.php in the theme. if there isn’t a functions.php file there yet then just create one and put that code in to remove the ‘quickpress’ widget and see if this helps. it did help on my sites and the errors were gone

    // Create the function to use in the action hook
    
    function removeDashboardWidgets() {
    	global $wp_meta_boxes;
    	// Remove the quickpress widget
    	unset($wp_meta_boxes['dashboard']['side']['core']['dashboard_quick_press']);
    
    } 
    
    // Hoook into the 'wp_dashboard_setup' action to register our function
    
    add_action('wp_dashboard_setup', 'removeDashboardWidgets' );

    please let me know if this improves things – thanks

    Thread Starter Becki Beckmann

    (@becki)

    hi otto,

    thanks for the reply

    where can i find those rewrite rules in the database? in the ‘options’ table?

Viewing 15 replies - 91 through 105 (of 113 total)