ianbee

Ok, really not sure what is different on your site than mine, but I have a completely vanilla install of WP and just that plugin installed, created 2 test posts each with the same MP3’s that you’re using on your site, and when I click them they play… =/

https://dev.alieneila.net/

Sorry for the late reply I was playing video games with my brother, but……OMG!!! WTF!! I don’t even know what to do right now, I even made a new blog and tested it there, still the same problem. Maybe its the jetpack plugin? What plugins do you have activated or installed on that dev.alieneila.net?

This is soooo weird! ??

And thanks for helping me out man

ahh ok =) Let me play with it on my dev site and I’ll let you know

Alright… If you manage to get it working, it would honestly mean sooooo much to me! And again, the links to mp3’s should play in the audio bar.

I look forward to hearing the results! ??

You need to check the plugin settings to see if there is an auto play option. When I clicked it, it loaded into the playbar and then when I clicked the play button it played just fine.

Thanks for the reply! It means a lot! There is an autoplay feature with the plugin, but that just automatically plays the most recent mp3 when you visit the website. I do not want to do that. The problem with the plugin is that when you click the link to the mp3 (10 – No Worries (DatPiff Exclusive) under the MP3 test post) it should automatically play in the audio bar at the bottom of the page. Instead, when you click on the link… it does nothing. And that is the problem.

You said when you clicked the link, it “loaded into the playbar” it did not actually load into the playbar once you clicked it. The song was loaded into the bar because the plugin just automatically loads the most recent mp3 on your blog. And for my blog, it only had one mp3 on it when you looked at the webpage. Now I have two mp3s on my blog, so you will see that it loads the most recent mp3.

So yeah, I’d just like the plugin to play the song in the playbar when you click on an mp3 link. It does this for the link I posted in OP.

Thanks for the help though bro! ??

I’ve tried changing the themes, links, everything. The links just don’t play in the audio player with the most recent version of wordpress. I think this is a big issue. If the creator of the plugin could adress this issue it would be awesome! Or if anyone else had this issue and has a fix.. feel free to contact me, my e-mail is [ redacted, support is offered via the forum and not email ]

Again, links to mp3’s do NOT play in the audio player with the most recent version of WordPress. And I’ve seen them work on earlier versions of WordPress.

I tried deactavating all my plugins accept n3rdskwat – mp3player, I tried creating .wav links instead of .mp3, I even tried creating a new blog and installing the plugin, but again the links don’t seem to work.

I think this is an issue with WordPress 3.4

If someone could please help me or let me know if it actually is an issue with WordPress 3.4.. that would be AMAZING!!! ??

Thanks for the help, I found out how to fix this issue, sort of. Will explain later ?? Thanks doe! ??

i think is_home may only work if the home page is the blog page, and is_front_page if static. Or, maybe try it with page id’s instead of page names.

Thanks for the feedback! My homepage is the blogpage and the frontpage is a static page. I tried doing what you said and entering the blog page’s ID instead of the page’s name… it did nothing. When I enter the PHP code is_home to change my header so it is different on the homepage, it breaks my header. With any other php code, it does nothing. So I know is_home is the correct coding to change the header on my blog page.

I don’t get why the slideshow header is showing up on my main blog page, when I’m telling it not to. But again, when I tell it to show a custom header for the page ( is_home )… the header breaks, and you can still see the slideshow header, when you shouldn’t be able to.

I hope that makes sense, and again, any help would be appreciated so much. If I’m not explaining myself fully or you don’t understand, please let me know and I will gladly try to help you understand. ??

@peter_l I tweeked the code a bit and it worked! thanks so much man! ??

My only suggestion would be to get away from timthumb and use the built in WordPress post thumbnail api.

Thanks, but I kind of have to use TimThumb. The theme I purchased (and there is little no none theme support being that the theme creator barely speaks English) uses custom fields to post thumbnails and there is a lot of coding that I would have to delete in order to stop using TimThumb and start using post thumbnail. I wouldn’t know where to begin even.

Deactivate all plugins and revert to Twenty Eleven theme and see if the problem persists.

The page I use timthumb on is used with a custom page layout. Therefor the page I’m using timthumb on will not be displayed on other themes. However, I did deactivate all the plugins and it still didn’t work ??

Anyone got any other suggestions?

Did anyone ever find out a fix for this? I have two of the same plugin widgets setup on two different websites and I only get this error message on one website… regulary.

If anyone could help or suggest a better latest tweets plugin / widget that doesn’t require entering any special authorization code for my twitter account, that would be awesome!

Resolved it by going into my content-extensions.php (probably different for most people) and replacing <?php the_excerpt); ?> with <?php the_content(); ?>.

Try adding this to the end of your style.css:

.cat-links {
border-right: 2px solid;
padding-right: 5px;
}
.meta-comments-link { padding-left: 5px; }

Thanks it worked! I orignally planed on doing it thru php only, but either way you get the same results. Again, Thanks! ??

In style.css:

1. On line 232 change this
background: url(images/bg2.jpg) black center top;
to this
background: url(images/bg2.jpg) black left top;
2. I don’t understand what you mean.

3. I can’t see what you mean.

4. To stop the background repeating, add this style to the body around line 232:
background-repeat: no-repeat;

Thanks so much for the quick reply!

1. I changed the coding to what you said, and the webpage still starts at the beginning of the header instead of the beggining of the background. (you can’t see the left of the background, just the right of the background past the content). So on a computer the webpage is shown in this horizontal order: background, content, background. But on a phone it shows in this horizontal order: content, background. Meaning, the left of the background is not showing. I hope this makes sense.

2. This is what I mean: When you goto the webpage on a phone you don’t see the whole webpage, you see the header zoomed in, then you have to zoom out to see the whole webpage.

3. This is what I mean: on a computer, theres a dark grey background for both the content and also the sidebar. On a phone, the background is only covering the content and not the sidebar. The content, sidebar and the whole webpage is all wraped around a contentwrapper that has a background image, this background image is only being wrapped around the content and not the sidebar (when on a phone).

4. I stoped the background repeating by entering in your code, but the background-attachment:fixed; code isn’t making the background stay in one spot on a phone.

I hope that makes it easier for you or anyone to understand, and again, any help would be appreciated sooooo much! ??

[ Please do not bump, that’s not permitted here. ]

If you haven’t a custom theme, when attempting to modify themes you should use a Child Theme or Custom Style/CSS plugin.

Have you a custom theme?

I downloaded a free theme thats mobile compatible called “Sundance”. But its edited heavily css and even php wise. I don’t know if that’s considered custom or not?

I just found the mobile settings, I listed them below. When I delete these settings from my css code, the site actually works a bit better on the phone – The sidebar is where it should be. When the code stays I run into theese problems when viewing my webpage on an Iphone:

-The sidebar gets pushed under my content instead of being on the right
-The webpage is auto zoomed in instead of zoomed out
-My content div isn’t as wide as it should be, its not covering the horizontal length of the sidebar as well as the actual content. It’s just covering the horizontal length of the content.
-You can’t see the left of the background, the website starts at the left of my content box instead of starting at the background.

Any help would be appreciated so much and here is the code:

/* =Responsive Structure
-------------------------------------------------------------- */

@media screen and (max-width: 1024px) {
	.flex-direction-nav {
		bottom: -36px;
		left: auto;
		margin: 0;
		right: 21px;
		top: auto;
		width: auto;
	}
	.flex-direction-nav li {
		float: left;
		margin: 0 1px 0 0;
	}

}

@media screen and (max-width: 768px) {
	.site-description {
		float: none;
		margin: 0.7857142857em 0 0 0;
		width: 100%;
	}
	#masthead hgroup {
		margin: 0 0 2.2857142856em 11.17886178%;
	}
	.site-content {
		float: none;
		margin: 0;
	}
	#content {
		margin: 0;
	}
	#secondary {
		float: none;
		width: 100%;
	}
	.hentry {
		margin: 0 0 3.1428571428em 11.17886178%;
	}
	.entry-header .avatar {
		margin: 9px 0 0 -12.58581235%;
	}
	#content .site-navigation {
		margin: 0 0 1.5714285714em 11.17886178%;
	}
	.syndicate,
	.widget {
		padding: 1.6666666666em 0 0 11.17886178%;
	}
	.page-header {
		margin: 0 0 3.1428571428em 11.17886178%;
	}
	.featured-content {
		float: none;
		width: 100%;
	}
	.featured-content-info {
		float: none;
		margin: 0;
		width: 100%;
	}
	.featured-summary p {
		padding: 0 0 2em 0;
	}
	.flex-direction-nav {
		bottom: -35px;
		left: 0;
		margin: 0;
		right: auto;
		top: auto;
		width: 100%;
	}
	.flex-direction-nav li {
		float: none;
	}
	.flex-direction-nav li a {
		left: 0;
		position: absolute;
		top: 0;
	}
	.flex-direction-nav li .prev {
		margin: 0 0 0 -6px;
	}
	.flex-direction-nav li .next{
		left: auto;
		margin: 0 -6px 0 0;
		right: 0;
	}
	.flex-control-nav {
		bottom: 0;
		left: 0;
		text-align: center;
		width: 100%;
	}
	#comments {
		margin: 0 0 1.5714285714em 11.17886178%;
	}
	.comment .avatar {
		margin: 3px 0 0 -12.58581235%;
	}
	#content .site-navigation.comment-navigation {
		margin: 0 0 1.5714285714em 0;
	}
	.error404 article .widget {
		padding: 1.6666666666em 0 0 0;
	}
	.syndicate li {
		margin: 0 0 0.933333333em 20px;
	}
	.syndicate li:first-child {
		margin: 0;
	}
}

@media screen and (max-width: 600px) {

	#page {
		padding: 3.1428571428em 0.5714285714em 0;
	}
	#masthead {
		margin: 0 0 3.1428571428em 0;
	}
	#masthead hgroup {
		margin: 0 0 2em 0;
	}
	.site-title {
		font-size: 22px;
		text-align: center;
	}
	.site-description {
		font-size: 12px;
		margin: 0;
		text-align: center;
	}
	.main-small-navigation {
		border-bottom: 1px dotted #b3b3b3;
		border-top: 1px dotted #b3b3b3;
	}
	.menu-toggle {
		font-size: 17px;
		line-height: 2.0em;
		margin: 0;
		text-align: center;
		text-transform: uppercase;
	}
	.menu-small-menu-container {
		margin: 0 auto;
		width: 50%;
	}
	.featured-posts-wrapper {
		margin: -0.8571428571em 0 4.7142857142em 0;
	}
	.entry-header .avatar {
		display: none;
	}
	.byline {
		display: inline;
	}
	.hentry,
	.full-width .hentry,
	.image-attachment .hentry,
	.no-sidebar .hentry,
	.error404 .not-found {
		margin: 0 0 3.1428571428em 0;
	}
	.entry-content, .entry-summary {
		margin: 1.5714285714em 0 0 0;
	}
	h1 {
		font-size: 22px;
	}
	h2 {
		font-size: 19px;
	}
	h3 {
		font-size: 17px;
	}
	h4 {
		font-size: 15px;
	}
	h5 {
		font-size: 14px;
	}
	.no-sidebar .page-header {
		margin: 0 0 3.1428571428em 0;
	}
	#comments,
	.full-width #comments,
	.image-attachment #comments,
	.no-sidebar #comments {
		margin: 0 0 1.5714285714em 0;
	}
	.comment .avatar {
		display: none;
	}
	#content .site-navigation,
	.no-sidebar #content .site-navigation {
		margin: 0 0 1.5714285714em 0;
	}
	.page-header {
		margin: 0 0 3.1428571428em 0;
	}
	.syndicate, .widget {
		padding: 1.6666666666em 0 0 0;
	}
	.site-footer {
		padding: 1.5714285714em 0 1.5714285714em 0;
	}
}
@media only screen and (min-device-width: 320px) and (max-device-width: 480px) {

	#page {
		padding: 1.5714285714em 0.5714285714em 0;
	}
	#masthead {
		margin: 0 0 1.5714285714em 0;
	}
	#masthead hgroup {
		margin: 0 0 1.1428571428em 0;
	}
	.featured-posts-wrapper {
		margin: -0.8571428571em 0 2.3571428571em 0;
	}
	.hentry {
		margin: 0 0 1.5714285714em 0;
	}
	.entry-content, .entry-summary {
		margin: 0.7857142857em 0 0 0;
	}
	.commentmetadata {
		margin: 0 0 0.9166666666em 0;
	}
	.entry-content embed,
	.entry-content iframe,
	.entry-content object {
		height: auto;
	}
}