I'm new to drupal, so I'm not sure whether this is a bug in the code, or something I've done wrong with my configuration, but I thought it best to put it up here, just in case.

Every time I change my settings on the module's config page, this error appears in my logs. As far as I can tell, it does not cause any problems in the module's actual operation, though.

Invalid argument supplied for foreach() in /home/fraz/public_html/o/modules/reptag/reptag.module on line 708

At present (this is a non-public site, testing things before it's ready to go live), only authenticated users have permission to use reptags, and they are only allowed to use one tag module - the bbcode one, with a few tags stripped out of the code (I did this myself, manually by making a copy of the tag module and editing it). I'm reasonably confident that this is not the issue, though, as the error persists even when the tag module is disabled.

I don't know if this would make any difference, but I do not have xajax installed.

Also, I'm not sure if this warrants a separate bug report, as I can't verify where it originates, but when I checked the "Enable Debugging" box and saved settings, I received a blank white page with only the word "NULL" printed at the top. Every subsequent time (I tried at least 3 times) that I went to the page to turn this option back off, I received this, and found that the option had not been disabled. I opened up the database to search for the appropriate flag, to switch it off, but before I had touched anything, I tried to change the option one last time... but it worked this time.

The error that appeared in the logs with this odd behaviour is this:
Cannot modify header information - headers already sent by (output started at /home/fraz/public_html/o/modules/reptag/reptag.module:254) in /home/fraz/public_html/o/includes/common.inc on line 266.

Comments

profix898’s picture

Hi EvilFraz!

Welcome to Drupal :) There are several updates for reptag 4.7 I will add the next days. Not sure your issue is already included, but I will check this. I'm a little busy at the moment, so it may take some time (till weekend, I think) for the updates to be committed.

EvilFraz’s picture

Thanks, profix898. I appreciate you replying to let me know what things are planned. :) It's nothing urgent, anyway - everything works as it needs to for me, I just figured I should report it in case it breaks something else, unseen, elsewhere. Great module, by the way - the method for defining your own tags is intuitive, and it really helps with what I'm working on.

profix898’s picture

Status: Active » Fixed

I have just fixed several issues that appeared since 4.7rc4 (including this one). Please update to the latest version.

... the method for defining your own tags is intuitive ...

Thanks :) The xajax version is even more intuitive. You can download a bundled package on documentation pages (http://www.profix898.de/files/drupal/reptag/reptag-4.7-xajax.tar.gz) or install xajax separately.

(In case this issue is not fixed for your configuration, set status back to active.)

EvilFraz’s picture

I can confirm that both bugs appear now to be fixed. Thanks. :)

I've tried out Xajax, and you're right, it does make things easier, although perhaps you misunderstood me when I said I was defining my own tags - I'm writing and uploading my own .tags modules. I'm fairly sure Xajax doesn't do anything to help with that, but please feel free to correct me if I'm wrong.

I have another question, but it fits more as a feature request, so I'll make a new post under that category shortly.

profix898’s picture

I'm writing and uploading my own .tags modules

Are your modules helpful to other users? If so, please consider to share them ...

I'm fairly sure Xajax doesn't do anything to help with that ...

Yep, you're right about that ... I thought you would use sidewide-/user-tags ...

EvilFraz’s picture

I'm afraid the tags in question are pretty site-specific, and I can't see anyone else finding them very useful, but regardless, when the site is live, I'll try and remember to come back and share whatever modifications I make that work properly and are running on my site. (I'll go back over them and try to make sure I haven't hardcoded any site addresses in them, too.)

Anonymous’s picture

Status: Fixed » Closed (fixed)