getTagProp not defind

[John Langer]

This was happening with CT312 installed. I've just installed v313 and still get the error.

If I try and run the behaviour "Clear Session Values" I get a warning dialog box that says:

"While executing onLoad in WACT_ClearSession.htm, the following JavaScript error(s) occurred:

At line 357 of file
"C;\Users\John\AppData\Roaming\DreamweaverCS%\en_US \Configuration\Shared|WebAssist\Cookies\Library\WA _configuration.js":
getTagProp is not defind"

I've deleted the WinCache file and recreated it. I don't really want to recreate the Configuration folder unless it's absolutely necessary and, as I've said, I've uninstalled Cookies toolkit 312 and installed CT313.

Line 357 of that file says, " return [getTagProp(tXML, "macromedia-extension", "name"), getTagProp(tXML, "macromedia-extension", "version"), getTagProp(findTag(tXML, "author", true), "author", "name")];"

Any ideas?

[Jimmy Wu]

Unfortunately it looks like there is another extension that is interfering with that server behavior. You will have to delete the configuration directory to get around it currently. We'll have to do some more testing to look into which extension is causing the interference.

[paulshoe379536]

I too am having the same problem (capture of error dialog attached).

I have uninstalled all 19 of my WebAssist extensions and reinstalled. I did not uninstall extensions from other sources. This did not resolve the issue. Unfortunately, it takes a lot of time to uninstall and re-install extensions. I hoping there is a solution that will not require me to do this again.

Using "Set Cookie Values" works.
When I access "Set Session Values" it launches the "eCart" activation screen.

[John Langer]

Unfortunately it looks like there is another extension that is interfering with that server behavior. You will have to delete the configuration directory to get around it currently. We'll have to do some more testing to look into which extension is causing the interference.
Thanks for the reply Jimmy. Are you actually looking into this now, or is it something for the future? I'f it's now, I'll hold on for a fix as deleting the config folder is a real pain, and if it's another extension interferring then it's likely to return anyway.

[Jimmy Wu]

Its something we're looking into for a future release, since it will take quite a bit of QA time to determine which extensions are causing the issue.

[John Langer]

OK Jimmy, thanks for the feedback.

Just off the top of my head (and I could be wrong) I'm sure CT worked fine until I installed Site Sculpture. Just an idea of where to start looking...

I'll leave things as they are until I really need that part (clear sessions) of the CT extension.

[Jimmy Wu]

Thanks for letting us know your experience. It'll definitely help with determining the cause if Site Sculptor is the cause.

[mrs]

Just to confirm, I am getting this error and I too have site sculptor.

Have you tried uninstalling both CT and SS, and then just installing CT again? I think I am going to try this, but just a thought!

I'll let you know if it makes a difference. And another thought; during initial installation of CT, I had a message that said an newer version of something or other existed, but, CT's update to CS5 came a few days after SS was released. Don't know if that's useful...

[Jimmy Wu]

Thanks for that feedback. If uninstalling like that fixes the issue, please post back and let us know.

[weboholic]

I have cleaned the user folder in roaming (win 7) and installed cookie toolkit, universal email and security assist in this order. After installing security assist cookie toolkit stop working with the known issue. I hope this helps to uncover the bug.

[Jimmy Wu]

Yes, thanks for posting back with that. I've verified that SecurityAssist and Cookies Toolkit together causes the error. I've updated the bug that was logged and hopefully we'll be able to come out with a fix for it soon.

[John Langer]

That's excellent news. Thanks for taking the time to investigate weboholic.

[John Langer]

Yes, thanks for posting back with that. I've verified that SecurityAssist and Cookies Toolkit together causes the error. I've updated the bug that was logged and hopefully we'll be able to come out with a fix for it soon.
Has this issue been addressed yet? If not is there a fix date scheduled?

[Jason Byrnes]

I do not have a date for when a fix will be available, but it should be released soon.

[designerwest]

I too have found after installing/reinstalling the other plugins that Secruity Assist for me is the bad egg that doesnt allow Cookie Assist to work fully.

would really appriciate a fix on this since i have paid for a suite of products that surely should work in union. the main purpose of purchasing your products was to cut down workflow lol

[Jason Byrnes]

We do not have a fix for the issue at this time. When we release an update to Security Assist the issue will be addressed.

[Steve Skinner]

I too have begun running into this issue with trying to use clear session values from the cookies toolkit. And yes, I do have the securityassist extension along with dataassist and a few other webassist extensions too.

Looking forward to this fix!

[Jason Byrnes]

It has been logged in our bugbase to be addressed when the next update of security assist is released.

[rmurphy6261468]

I had the same error. After uninstalling Security Assist, Cookies Toolkit worked fine. I then reinstalled Security Assist, and got the error again. Subscribed to the thread and waiting... RM

[pbartelt102585]

No solution in sight?

[Jason Byrnes]

see the following post for a fix to the issue:
http://www.webassist.com/forums/showpost.php?p=81655&postcount=2

[nickj]

This thread is almost six months old has anyone found a solution?

Thanks

Nick

[Jason Byrnes]

see the following post for a fix to the issue:
http://www.webassist.com/forums/showpost.php?p=81655&postcount=2