Forum Replies Created

Viewing 15 replies - 361 through 375 (of 408 total)
  • Thread Starter Robert S

    (@rschilt)

    Hi K,

    I upgraded to latest release of PM (2.5.4) and now get the following errors when updating own profile and also others…

    Warning: Invalid argument supplied for foreach() in ****/mydomain/wp-content/plugins/projectmanager/admin/admin.php on line 1117
    Warning: Cannot modify header information – headers already sent by (output started at ****/mydomain/wp-content/plugins/projectmanager/admin/admin.php:1117) in ****/mydomain/wp-includes/pluggable.php on line 850

    Hope the above info helps.

    R

    Thread Starter Robert S

    (@rschilt)

    Hi K,

    Thanks for responding.

    It’s not a major issue as the profile is updated despite the error message. However this error does happen every time I edit and save a profile – not just now and then.

    Incidentally have not seen the error when editing/saving a page/post.

    Regards,

    R

    Thread Starter Robert S

    (@rschilt)

    Hi,

    Thanks for responding and fixing that issue.

    Have fired up and all seems to be working great!

    Just one thing…. it does not seem to be excluding my comments and I’m setup as an administrator. Any reason you might be aware why the plugin would be behaving this way?

    R

    Thread Starter Robert S

    (@rschilt)

    K,

    1.6.1 working like a dream!

    R

    Thread Starter Robert S

    (@rschilt)

    Hey guys,

    I had the same issue with 1.6 and have reverted back to 1.6beta which works fine.

    R

    Thread Starter Robert S

    (@rschilt)

    K,

    I have reinstalled the beta version as it works fine.

    R

    Thread Starter Robert S

    (@rschilt)

    K,

    Sorry to tell you this but the same issue has surfaced with 1.6
    Where’s that beta version?

    R

    Thread Starter Robert S

    (@rschilt)

    K,

    Trust Windows to foul up on something as simple as that!

    R

    Thread Starter Robert S

    (@rschilt)

    K,

    Apologies for the duplicate post (delete the other one if you can)

    Just tested a couple of things and answered some of my own questions

    1) If a term/acronym is already linked then acronyms adds on top of what is already there… cool!

    2) Acronyms can have spaces in them (eg: Tok Pisin).

    3) The plugin is case sensitive. If there’s an entry in acronyms table “Tok Pisin” then “tok pisin” will not be recognised by the plugin. Anyway of making your plugin case insensitive – or perhaps making that an option?

    R

    NB: From the little testing I have done so far… I like what I see!

    Thread Starter Robert S

    (@rschilt)

    K,

    A quick post to let you know that I have tested 1.6b and so far I have not been able to fault it. Looks like you cracked it bro!

    All the issues I was having previously when activating, creating a new post and deactivating the plugin seem to have been fixed.

    Are you able to share with us what the issue was in the end?

    Thanks for persisting.

    R

    Thread Starter Robert S

    (@rschilt)

    K,

    Understand the frustration. As with all technical problems – there’s always a solution. In the end it will be something simple (for than likely) and you would have learnt that little bit more.

    Will keep my eyes open for any updates of your plugin and test as they become available.

    Regards,

    R

    Thread Starter Robert S

    (@rschilt)

    K,

    Doesn’t look like we are having any luck getting hold of each other on GTalk.

    Thought I’d give the DEV version another go and interestingly – on activation it comes up with the original message:

    Warning: Cannot modify header information – headers already sent by (output started at …/wp-content/plugins/acronyms/acronyms.php:1) in …/wp-content/plugins/bad-behavior/bad-behavior/screener.inc.php on line 8

    Honestly, I don’t have the time to be involved in further testing. What I will do is keep my out for future versions. Perhaps as more folks take your plugin for a test run – some of these “kinks” will be ironed out.

    Regards,

    R

    Thread Starter Robert S

    (@rschilt)

    Hi,

    Apologies for perhaps not being clear in my previous response. The bit about “the author” was directed at “oncletom”. I have been aware since first posting to this forum that “ketsugi” is the plugin author.

    Anyway…

    I have tried a couple of times to contact you via GTalk. Note that I’m not much of a “chat” user as I access the internet over dialup type speeds and we still have timed calls where I am (Papua New Guinea).

    I suppose we also have the time zone differences – when you’re asleep – I’m awake – and vice-versa.

    Forget about AIM – lets GTalk… my id is “rjschilt@gmail.com” – please keep your eye out for “jungle” boy.

    R

    Thread Starter Robert S

    (@rschilt)

    Very odd…

    I have checked and rechecked my “acronyms.php” and I don’t have a white space as you mention. When I saw that error it’s the first thing I looked for.

    I am curious about one thing… if the SVN sourcecode does not have the whitespace then how did it end up in your local copy of “acronyms.php”? Isn’t that where the plugin package is actually downloaded from?

    Lets hope that the author is able to resolve this issue – I rather like the idea of what his plugin can offer.

    R

    Thread Starter Robert S

    (@rschilt)

    Had a go on my test blog…

    1) Acronyms activates without any issues.

    2) When going into “New Post” get the following error:

    Warning: Cannot modify header information – headers already sent by (output started at …/wp-content/plugins/acronyms/acronyms.php:1) in …/wp-includes/classes.php on line 1571

    Looks like we are slowly getting there but not quite there yet.

    R

Viewing 15 replies - 361 through 375 (of 408 total)