Author Topic: Warning: strstr() [function.strstr]: Empty delimiter in  (Read 3766 times)

bassfisherd

  • Newbie
  • Posts: 5
Warning: strstr() [function.strstr]: Empty delimiter in
« on: March 05, 2013, 12:36:06 am »
I am receiving this error - Warning: strstr() [function.strstr]: Empty delimiter in /home/content/34/7828134/html/geektastic/wp-content/plugins/powerpress/powerpress.php on line 1979

I get that error each time i have an audio file within my posts. Any help on this issue would be greatly appreciated!

my site is geektasticpodcast.com - you can see that it does it to every podcast/audio file


mgdell

  • Blubrry Customer Support Coordinator
  • Administrator
  • Hero Member
  • *****
  • Posts: 3318
Re: Warning: strstr() [function.strstr]: Empty delimiter in
« Reply #1 on: March 05, 2013, 09:35:37 am »
To troubleshoot this, try uninstalling powerpress. And then re-install it.  This will make sure that the files you have in the powerpress plugin are not corrupt.

If that doesn't solve it, try deactivating other plugins one by one until you find one that clears up the problem. If that doesn't work, try switching to the default wordpress theme (2011 or 2012) and see if it clears up.

It could be a plugin conflict or a theme conflict. 

Angelo might have some more insight on the error also.

-Mike

angelo

  • CIO, RawVoice
  • Administrator
  • Hero Member
  • *****
  • Posts: 4483
Re: Warning: strstr() [function.strstr]: Empty delimiter in
« Reply #2 on: March 05, 2013, 03:30:07 pm »
Mike, this is a notice/warning message from PHP, it's in the PowerPress code whether he re-installs or not.

bassfisherd, what version of PHP are you using?

bassfisherd

  • Newbie
  • Posts: 5
Re: Warning: strstr() [function.strstr]: Empty delimiter in
« Reply #3 on: March 09, 2013, 12:01:32 am »
where do i find that out?

angelo

  • CIO, RawVoice
  • Administrator
  • Hero Member
  • *****
  • Posts: 4483
Re: Warning: strstr() [function.strstr]: Empty delimiter in
« Reply #4 on: March 09, 2013, 12:09:04 am »
Go to PowerPRess menu, "Tools" menu option (in the left) then click the "Diagnostics" option.

I believe I fixed the possibility of this bug in the next release, even so, if you can tell me what version of PHP it will confirm if the fix I have in place will work or not. You're hopefully using a version of PHP 5.3 or newer.

bassfisherd

  • Newbie
  • Posts: 5
Re: Warning: strstr() [function.strstr]: Empty delimiter in
« Reply #5 on: March 09, 2013, 12:17:28 am »
WordPress Version 3.5.1

Your version of PHP (5.2.17) is OK!


i copied and pasted that

angelo

  • CIO, RawVoice
  • Administrator
  • Hero Member
  • *****
  • Posts: 4483
Re: Warning: strstr() [function.strstr]: Empty delimiter in
« Reply #6 on: March 09, 2013, 12:32:05 am »
Hmm, 5.2.x should be ok I think, I have to recheck the documentation for the strstr function.

angelo

  • CIO, RawVoice
  • Administrator
  • Hero Member
  • *****
  • Posts: 4483
Re: Warning: strstr() [function.strstr]: Empty delimiter in
« Reply #7 on: March 09, 2013, 12:33:35 am »
Yep, specifically 5.2.4 or greater. So the next update to PowerPress will fix this. If you don't want to wait, I can give you the URL where you can download the development zip so you can install it manually.

bassfisherd

  • Newbie
  • Posts: 5
Re: Warning: strstr() [function.strstr]: Empty delimiter in
« Reply #8 on: March 09, 2013, 12:40:58 am »
i would greatly appreciate the link.


thank you for all your help!!

angelo

  • CIO, RawVoice
  • Administrator
  • Hero Member
  • *****
  • Posts: 4483
Re: Warning: strstr() [function.strstr]: Empty delimiter in
« Reply #9 on: March 09, 2013, 01:03:36 am »
Here's the dev version, it's almost ready for release but I want to fix one other small issue over the weekend before I push it out.

http://downloads.wordpress.org/plugin/powerpress.zip

Download, unzip, upload over the existing wp-content/plugins/powerpress folder, and see if the problem goes away.

bassfisherd

  • Newbie
  • Posts: 5
Re: Warning: strstr() [function.strstr]: Empty delimiter in
« Reply #10 on: March 09, 2013, 01:41:36 am »
it worked... thank you so much!!!

Cat Williams

  • Newbie
  • Posts: 6
Re: Warning: strstr() [function.strstr]: Empty delimiter in
« Reply #11 on: April 13, 2013, 10:42:50 pm »
I'm having the same problem. I tried de-activating and then deleting the plug in and re-installing but still getting the same errors. I wish there was a customer service number to call! My client is freaking out.

angelo

  • CIO, RawVoice
  • Administrator
  • Hero Member
  • *****
  • Posts: 4483
Re: Warning: strstr() [function.strstr]: Empty delimiter in
« Reply #12 on: April 13, 2013, 10:59:21 pm »
You can schedule a consult with us, go to the http://create.Blubrry.com site for consulting details.

Or follow the instructions on this thread and install the Dev version. Or wait till the next release.

angelo

  • CIO, RawVoice
  • Administrator
  • Hero Member
  • *****
  • Posts: 4483
Re: Warning: strstr() [function.strstr]: Empty delimiter in
« Reply #13 on: April 14, 2013, 10:26:39 am »
I replied late last night while watching a movie with my wife. I saw your tweet, let me clarify...

Quote
I wish there was a customer service number to call! My client is freaking out.

If you want to speak with someone on the phone, you can hire us as consultants. (This is a free open source plugin, if you want free help then you have to use the forums here and when we have free time we'll help you).

Quote
I'm having the same problem

If you read this entire thread, specifically my reply on March 09, 2013, 01:03:36 am, I explain how to download the dev version and install it as I've fixed the problem, it's just not released yet.

And if you an just wait a few more days, I will be releasing this update that fixes this problem.
« Last Edit: April 14, 2013, 10:30:37 am by angelo »

Cat Williams

  • Newbie
  • Posts: 6
Re: Warning: strstr() [function.strstr]: Empty delimiter in
« Reply #14 on: April 14, 2013, 11:33:59 am »
Since this thread is old, I assumed that your answer to the previous commenter "it's almost ready for release" on March 9th meant you had already updated the program by April 13. But yes, that is eventually what I had to do to fix the issues.