Support Forum
Support Forum
Offline
I can see that the PM button doesn't have onclick='spjDialogAjax(this, "http://
or this href="javascript:void(null)"
Both watch and subscribe button markup shows that, I can't see any other differences.
Offline
Are you just looking for the CSS source of the number? If so then you need to look in the sp-pm.spcss file which is what controls it when using Reboot. Unless you have removed the file of course.
 |
YELLOW
SWORDFISH
|
Offline
I want to know why it isn't calling the correct css from sp-pm.css, I can't see the error within the markup and it's not browser or OS related, from where I'm standing it's a coding issue but I just can't see it - I've gone code blind.
Everything is out of the box, nothing has been moved or modified, all files are exactly the same as the install on my dev server which was a fresh install. The sp-pm.css is as it comes - no changes made, I have made like for like comparisons and checked for file corruption all to no avail. No files have been altered/modified within the SP structure whatsoever with the exception of the additional overlays that is. I'm going to run tests on the vanilla install to see if the issue exists there. Back in 20 mins or so...
Offline
The same issue exists on the fresh install so it's apparent to me it's the PM plugin coding thats the issue and nothing to do with the site I'm working on.
Offline
Yes, that's right because Reboot doesn't display anything other than the standard font colour for unread PM's.
In your post #5, it looks to me like you are editing the actual plugin CSS file which is incorrect. As Andy has said above, Reboot has it's own CSS files for plugins in the 'styles' folder. Here you should find sp-pm.spcss, not sp-pm.css. In the spcss you will see that Reboot defines the colour as the standard font colour i.e:
#spMainContainer #spPmCount .spPmCountUnread {
color: <?php echo($lightFont); ?>;
}If you want it to display red for all overlays, the easiest thing to do would be to create a child theme, bring in the spcss file and change the 'color' to a hex number instead of a variable, this way it will only get the rule from the spcss file for all overlays i.e:
#spMainContainer #spPmCount .spPmCountUnread {
color: #FF0000;
}
Offline
nothing is being editied!
You guys are confusing to say the least, one of you says the colour change should happen (post 2) the other 2 say otherwise.
If watch and subscribe go red when new content is showing then doesn't it make sense that the pm button should react the same way? I shouldn't need to be creating child themes you guys should have this tied up TBH.
Offline
OK to clear things up, let's forget the word 'edited', and just say 'looking' at the wrong file.
Andy is right in post no.2 when he says it should change, although you hadn't told us you were running Reboot until afterwards, which makes all the difference when speculating.
Actually yes you are right, we should have this 'tied up', but Reboot is a relatively young theme in that it was only released in the early part of the year, and without feedback on these issues some of them are not always easy to spot. In fact this issue by the look of things has not only been present for quite some time, but never reported by any other members up until now!
Having looked into the subscriptions and watches .spcss files I can see that actually they do specify a hex number for the unread count, whereas for some reason PM's don't. It should really be all one way or the other, so I will make sure that the next update to Reboot includes a fix to change the colour of the unread PM count to red.
Hopefully we will have the next update out within the next week or so, so depending on what you want to do - you can either wait for the fix, or edit the .spcss file. If you do choose to edit the file then there would be no need to make a child theme as the update will include the fix.
Offline
Thank you Ike that's the answer I was waiting for
You need to bare with me, I suffer bipolar so I can go off on tangents, think at 500mph and be very pedantic.
I investigated this issue a few weeks back but got sidetracked by another job, I can only apologise for not putting all the install details in my first post, which would have made the issue a bit clearer to you guys.
I will wait for updates because it isn't my site, the admins there can cope with updates but's thats the limit of their abilities. They actually paid for this subscription for me to obtain reboot and the plugins they wanted. I have no idea of the SP history as I usually do Vbulletin and phpBB stuff, both SP & WP are new to me. I'm just paid to look at root causes of the errors and issues on this particular site, putting it all in order so to speak.
Thanks guys - I like it when an Issue is resolved 
All RSS1 Guest(s)