While browsing any term page (Category.module here) i do get the following warning repeated 2 times:
warning: strpos() [function.strpos]: Offset not contained in string. in /home/kiteatla/public_html/drupal/modules/ad/embed/ad_embed.module on line 233.
tx
Comments
Comment #1
jeremy commentedI'm not familiar with the category module. If you disable the category module, does the problem go away?
Comment #2
marcoBauli commentedbasically Category.module transforms any term and vocabulary into a node, and makes use of a wrapper (taxonomy.module.wrapper) that replaces default core taxonomy.module, adding all the functions needed by Category (just an unpretentious brief description from a user to give an idea of what Category does ;)
Now, completely disabling Category and all it's contrib modules, and replacing the core Taxonomy.module:
• if i visit
/taxonomy/term/xi do not get any warning.• if i visit the node previously created by Category for that taxonomy term (
/node/x) the warning is still there.Sorry i cannot give any more hint, but please just ask and i'll be happy to provide feedbacks.
Oh, just FYI i remember also the old Banner.module had some integration issues with Category. Thank you for considering
Comment #3
nathanraft commentedI get the same error and am only using taxonomy.
Comment #4
jeremy commentedNathanRAFT, where do you see this error? Please provide steps for duplicating it.
Comment #5
nathanraft commentedWhen I select either of the following options... the error only shows on the frontpage.
Manually embedded ads
Configuration options for manually embedded ads using [[ad]] and
tags.
Replace ad bracket tags
Replace [[ad]] style tags in site content with advertisements.
Replace ad comment tags
Replace
style tags in site content with advertisements.
Hope this helps.
Comment #6
jeremy commentedI've been unable to duplicate this whatever I try. However, it seems that what's happening is a blank teaser is being passed into ad_embed_replace() causing strpos() to throw a warning. I've added tests to prevent this from happening and checked the fix into the 4.7.x and 5.x development trees. It will be included in -beta9 and the nightly development builds.
Comment #7
(not verified) commented