cewebster

You’re not the first person to tell me it looks fine on their Firefox. I’ll have to check on blocking Javascript (? I don’t think it is), because other Firefox users at my organization saw it too.

For now I went into the K2 options in the theme editor and clicked “Disable rolling archives” so that the problem feature doesn’t even appear at the top of the page.

Takes care of my immediate problem, so I’ll mark this resolved, thanks. I am still interested in the solution, but it’s not affecting the appearance of my blog at the moment.

Thanks for the replies.

Using tabs to force paragraph breaks was a nightmare when I worked in print design. You couldn’t reformat the text without huge white rivers of space showing up in the wrong places needing tons of cleanup.

In general using “intentional tab characters to start new paragraphs” is just a bad idea because html editors don’t deal well with tabs either. The equivalent of the hard return in print is the <p>and </p> tag to enclose a paragraph in html. Even multiple <br>‘s would be better.

Maybe check out some basic html tutorials online and use the conventional tags to format what you need. Starting off with code as clean as possible gives you better odds of stuff working.

From a tip on something else on the K2 forums, I went into the K2 options theme editor and disabled rolling archives. That works for now without a lot of posts to sort out. The slider and older and newer links don’t even appear now at the top of the page.

I still have a link at the bottom of the page that says “Previous entries” or “Newer entries” depending on which page you are on.

This takes care of my immediate problem.

If someone comes up with a Firefox fix, I’d still be interested.

Thanks

woopsie, sorry. I should be using mindreader energy for solving my problem!

https://dce.unm.edu/dceblog/

The slider errors in Firefox and disables the “newer” and “older” buttons too.

Thanks for the info.

I did a search for “slider” in the K2 files and came up with deleting the line that says,

<script type="text/javascript" src="<?php bloginfo('template_directory'); ?>/js/slider.js.php"></script>

in the header.php. In hopes this would keep that script from running. However, this kept the “older” and “newer” buttons from even being operational in Safari, which was working before. So I put it back.

I am more leery of breaking things if I go into the slider.js.php file, so if anyone has any guidance, still much appreciated.`

FWIW, this is how I changed login redirect and site admin tabs on a modified K2 site. I will have several authors and public commenters will be required to register as subscribers. The login redirect now goes to the main blog page and the admin tab reads “My Profile” and goes to the profile page instead. Novice type users never have to deal with the dashboard, though I can get there if I need to using the browser address bar. The other posters have access to the write and manage tabs from their profile.

1) Changed line 170 of wp-login.php to

$redirect_to = ‘index.php’;

((I changed wp-admin to index.php))

2) Changed line 7 of /wp-admin/menu.php to

$menu[20] = array(__(‘Dashboard’), ‘read’, ‘index.php’);

((I changed value from 0 to 20))

3) Changed line 47 of template-functions-general.php to:

$link = $before . ‘^a href=”‘ . get_settings(‘siteurl’) . ‘/wp-admin/profile.php/”^’ . __(‘My Profile’) . ‘^/a^’ . $after;

((I changed /wp=admin/ to /wp-admin/profile.php/ and Site Admin to My Profile. On code excerpt above I changed the <> around the a tags to ^ so that the code would show up here and not convert to a link.))

This was the simplest approach and worked great for us. The commenters and the other people who write posts at our org can click on “my profile” and go to something familiar that makes sense, without being thrown by landing at the dashboard. I just let people sign up on their own and change the roles of internal people who want to post.

It’s pretty easy maintenance.

I’m not an expert and can’t help you if this doesn’t work. It worked well for me tho and didn’t break my site. I also came across a caution that this is changing core code and would need to be redone after a wordpress upgrade.

This is what the line looks like that turned into a link in the post above. I converted the expected <> around the “a” tags into ^ so the code would show up instead of the link:

$link = $before . ‘ ^a href=”‘ . get_settings(‘siteurl’) . ‘/wp-admin/profile.php/”^’ . __(‘My Profile’) . ‘^/a^’ . $after;

FWIW, this is how I solved this on a modified K2 site. I will have several authors and public commenters will be required to register as subscribers. I just changed the login redirect and site admin tab and the dashboard privileges and that took care of it without a lot of work. The login redirect now goes to the main blog page and the admin tab reads “My Profile” and goes to the profile page instead. Novice type users never have to deal with the dashboard, though I can get there if I need to. The following cites the line changed and which file it was in:

1) Changed line 170 of wp-login.php to

$redirect_to = ‘index.php’;

((I changed wp-admin to index.php))

2) Changed line 7 of /wp-admin/menu.php to

$menu[20] = array(__(‘Dashboard’), ‘read’, ‘index.php’);

((I changed value from 0 to 20. I also saw where someone had changed ‘read’ to ‘manage_options’ instead.))

3) Changed line 47 of template-functions-general.php to:

$link = $before . ‘‘ . __(‘My Profile’) . ‘‘ . $after;

((I changed /wp=admin/ to /wp-admin/profile.php/ and Site Admin to My Profile.))
ETA that part of the above code turns into a link after posting on the forum and is confusing. Here it is hopefully more as it appears, I just took out the expected <> around the “a” tags and replaced with ^:

$link = $before . ‘ ^a href=”‘ . get_settings(‘siteurl’) . ‘/wp-admin/profile.php/”^’ . __(‘My Profile’) . ‘^/a^’ . $after;

This was the simplest approach and worked great for us. The login going to the blog’s home page makes more sense to everyone. The commenters and the other people who write posts at our org can click on “my profile” after they log in and go to something familiar that makes sense, without being thrown by landing at the dashboard. I just let people sign up on their own and change the roles of internal people who want to post for them.

It’s pretty easy maintenance. WordPress rules. Note that I am not an expert and can’t guarantee this nor can I help you fix it if you break it. I did this without breaking my site tho and of course you should always back up the files first.

If you want to see it in action, go to https://dce.unm.edu/dceblog

FWIW, this is how I changed login redirect and site admin tabs on a K2 hack site. I will have several authors and public commenters will be required to register as subscribers. The login redirect now goes to the main blog page and the admin tab reads “My Profile” and goes to the profile page instead. Novice type users never have to deal with the dashboard, though I can get there if I need to. The other posters have access to the write and manage tabs from their profile.

1) Changed line 170 of wp-login.php to

$redirect_to = 'index.php';

((I changed wp-admin to index.php))

2) Changed line 7 of /wp-admin/menu.php to

$menu[20] = array(__('Dashboard'), 'read', 'index.php');

((I changed value from 0 to 20))

3) Changed line 47 of template-functions-general.php to:

$link = $before . '<a href="' . get_settings('siteurl') . '/wp-admin/profile.php/">' . __('My Profile') . '</a>' . $after;

((I changed /wp=admin/ to /wp-admin/profile.php/ and Site Admin to My Profile.))

This was the simplest approach and worked great for us. The commenters and the other people who write posts at our org can click on “my profile” and go to something familiar that makes sense, without being thrown by landing at the dashboard. I just let people sign up on their own and change the roles of internal people who want to post.

It’s pretty easy maintenance. WordPress rules.

If you want to see it in action, go to https://dce.unm.edu/dceblog

FWIW, this is how I changed login redirect and tabs on a K2 hack site. I will have several authors and public commenters will be required to register as subscribers. The login redirect now goes to the main blog page and the admin tab reads “My Profile” and goes to the profile page instead. Novice type users never have to deal with the dashboard, though I can get there if I need to.

1) Changed line 170 of wp-login.php to

$redirect_to = ‘index.php’;

((I changed wp-admin to index.php))

2) Changed line 7 of /wp-admin/menu.php to

$menu[20] = array(__(‘Dashboard’), ‘read’, ‘index.php’);

((I changed value from 0 to 20))

3) Changed line 47 of template-functions-general.php to:

$link = $before . ‘‘ . __(‘My Profile’) . ‘‘ . $after;

((I changed /wp=admin/ to /wp-admin/profile.php/ and Site Admin to My Profile.))

This was the simplest approach and worked great for us. The commenters and the other people who write posts at our org can click on “my profile” and go to something familiar that makes sense, without being thrown by landing at the dashboard. I just let people sign up on their own and change the roles of internal people who want to post.

It’s pretty easy maintenance. WordPress rules.

If you want to see it in action, go to https://dce.unm.edu/dceblog