Forum Replies Created

Viewing 15 replies - 1 through 15 (of 15 total)
  • Thread Starter bloggitivity

    (@bloggitivity)

    Little update:

    On the Site Stats page, I can click on “views today” and get to the usual detailed view.
    Clicking on a single day in the “mini view” or on the graph still gives me the 404 error.

    Here is the difference:

    Clicking on “views today” gets me to a …/wp-admin/admin.php?page=stats&… url
    Clicking on a bar in the graphic gets me to a …/my-stats/?… url (and the 404 error)

    The “…” part is the same again in both urls

    So there still is a way to view the details. But I’m still not sure why the usual way no longer works.

    Exact same problem here that MarjWyatt describes on both my sites running WP 3.2.1 with Jetpack 1.2.2. Getting the “We were unable to get your stats just now. Please try again.” but can view the ongoing stats after clicking on “View all”.

    So it works, but it’s certainly an inconvenience.

    Thread Starter bloggitivity

    (@bloggitivity)

    Why don’t we leave the definition of what are appropriate questions to the moderators?
    And why don’t we leave petty arguments out altogether?
    I’ve your feelings are hurt because I don’t deem your answer or your manner of answering helpful, sorry.
    But I rather react to an answer by saying it didn’t help me, indicating that I’m still in need of help, than not answer and therefore make someone who might be able to help think that no additional tips are required.

    I’m not entirely sure I understand your problem. Is “site” you are talking about – the “site” you want your visitors to see first – a WordPress page? And your problem is that visitors first land on the blog portion of WordPress and not on that page?

    If that is the problem, go to Settings > Reading
    Under “Front page displays” click on the “A static page (select below)”, then define your static page accordingly.

    Thread Starter bloggitivity

    (@bloggitivity)

    As much as I appreciate the spirit of trying to help, I’m looking for actual help, not vague soundbites.

    So if someone sees where I’m going wrong or where I’m missing something by looking through the two code batches above, please let me know what to put into the template file (and preferably where).

    If you need additional info, let me know.

    Thread Starter bloggitivity

    (@bloggitivity)

    I’ve tried that. Unsuccessfully.

    The theme in question has no pages.php, so the index.php is the next one to look at, isn’t it?

    Overall, there are the following files:

    comments.php
    footer.php
    functions.php
    header.php
    index.php
    rtl.css
    sidebar.php
    style.css
    template-fullwidth.php (a template without a sidebar, unlike the default page with a sidebar and a narrower content column)
    template-links.php (calls up the blogroll)
    template-wp-easyarchives.php (not even sure what that does)
    … and two templates that I created myself

    So yeah, the index.php seems to be where the answer lies. Only that I can’t find the answer.

    Index.php looks like this http://pastebin.com/MnTp13Rq

    Thread Starter bloggitivity

    (@bloggitivity)

    The build I’m working on is still local on my computer. The blog is currently running with a different page setup and a different theme. Sorry, could have mentioned that in the initial post.

    But any additional info you need I’ll be happy to provide as far as I can.

    Thread Starter bloggitivity

    (@bloggitivity)

    Found the solution myself.

    Thread Starter bloggitivity

    (@bloggitivity)

    New development:

    I have switched to the “Nest” theme, which natively supports one navigation menu location.

    In the header.php, I have added the following code

    <?php if( is_page(array('9,11,13,15')) ) wp_nav_menu( 'a');
    else wp_nav_menu('b'); ?>

    With “a” and “b” representing the two menus I have defined in the Appearance > Menu area of the WP backend.

    This has the effect, that menu A is displayed instead of the default menu of all pages. So partial success.
    BUT menu A is now displayed on all pages, not just just those with the page IDs I have defined.

    Thread Starter bloggitivity

    (@bloggitivity)

    Nope, that isn’t the solution either.

    Thread Starter bloggitivity

    (@bloggitivity)

    Custom menu was my first thought. They are convenient to set up and maintain.

    But honestly, I’m not opposed to a different solution.

    Thread Starter bloggitivity

    (@bloggitivity)

    I’ll try to explain again.

    In the theme I am currently using (Comet) supports two different locations for navigation menus by default (located in the header, not in the widget area/sidebar).
    One of them is above the page title, one of them below the title.

    I want to use the navigation menu called “Below Title”.

    For one group of pages, I want a menu that displays only those pages … in that very location.
    For the second group of pages, I want a menu with different entries … but in the same location.

    I am now looking for a way to define: all pages of group “A” will display menu “A” in the “Below Title” location while all pages of group “B” will display menu “B” in the “Below Title” location.

    Thread Starter bloggitivity

    (@bloggitivity)

    Or maybe someone can point out where my mistake is in my current approach.

    Step 1, I need to register one of the two menus I want to use (no need to register both, since I can use the already registered default (called “Below Title”) as the second menu, correct?).

    So in the functions.php, what looked like this:

    register menus
    */
    add_action( 'init', 'register_my_menus' );
    
    function register_my_menus() {
    	if ( function_exists('register_nav_menus') ) {
    		register_nav_menus( array('primary-menu' => 'Above Title','secondary-menu' => 'Below Title',) );
    	}
    }

    Should become

    register menus
    */
    add_action( 'init', 'register_my_menus' );
    
    function register_my_menus() {
    	if ( function_exists('register_nav_menus') ) {
    		register_nav_menus( array('primary-menu' => 'Above Title','secondary-menu' => 'Below Title', 'Custom' => 'custom', ) );
    	}
    }

    Then in the page.php, I add this:

    <?php if( is_page(array(9,11,13,15)) ) get_sidebar( 'custom');
    else get_sidebar(); ?>

    With 9,11,13,15 (and potentially more) being the page IDs of the pages I want this custom menu to replace the default menu (the secondary menu/below title).

    And then I need a new php that defines the custom menu to be located where the secondary menu is? Yes? No? If so, what needs to be in there?

    Thread Starter bloggitivity

    (@bloggitivity)

    1. Alright. Thanks for clarifying.

    2. I know it’s probably well meant, but a “go look it up and piece it together yourself” suggestion wasn’t what I was hoping for from asking here. That’s what I’ve been trying these past days and it didn’t get things to work. As I mentioned above: coding experience is there, but it is limited.

    Maybe someone has had the same problem and found a solution – or has done the same thing and never saw it as a problem – and can share the solution.

    I know it shouldn’t be too much coding, but I’m just not getting the code right and/or put it in the wrong place.

    Thread Starter bloggitivity

    (@bloggitivity)

    Two things.

    1. Sidebar for a menu in the header? Is that the right approach?

    2. I appreciate the suggestion, any suggestion, but this is extremely vague. At least for my limited coding experience. It’s like I am at point A and need to get to F, and you suggest E, which would lead to F, but leave out step B, C and D.

Viewing 15 replies - 1 through 15 (of 15 total)