also @ TechSpot: Microsoft's Indian online store hacked, passwords and user data exposed
Welcome to the TechSpot OpenBoards. Please read the FAQ if you have any questions. Sign up or Login to participate.

Go Back   TechSpot OpenBoards > TechSpot Editorial and Site Feedback > Site Feedback and Suggestions

Collaborate in the cloud with Office, Exchange, SharePoint, and Lync

Picture Commenting causes "Invalid Call to Script" Error

Reply
Thread Tools Search this Thread
  #1  
Old 06-03-2008
Obi-Wan Jerkobi's Avatar
TechSpot Booster
 
Location: New York
Member since: Feb 2008, 592 posts
System specs
Picture Commenting causes "Invalid Call to Script" Error

It's been happening since the new server was set up. Whenever I try to comment on a picture in gallery, I receive an error that says "Invalid Call to Script".
  #2  
Old 06-04-2008
Julio's Avatar
TechSpot Executive Editor
 
Location: Ecuador
Member since: Feb 2002, 5,352 posts
System specs
Thanks for the feedback Obi Wan, let me look into this.
  #3  
Old 06-04-2008
Julio's Avatar
TechSpot Executive Editor
 
Location: Ecuador
Member since: Feb 2002, 5,352 posts
System specs
I think I have fixed this now and picture uploading seems to be working again too
  #4  
Old 06-04-2008
Obi-Wan Jerkobi's Avatar
TechSpot Booster
 
Location: New York
Member since: Feb 2008, 592 posts
System specs
Thanx, Julio!
  #5  
Old 02-17-2009
Newcomer, in training
 
Member since: Feb 2009, 5 posts
Any idea what caused this problem? I have been coming across it on another forum also, and it is quite frustrating
  #6  
Old 02-17-2009
Ex-TechSpotter
 
Member since: Dec 2007, 18,354 posts
You need to find out on that forum. ie the support staff on the "other" forum must look into this. There are too may possibilities to suggest
  #7  
Old 02-17-2009
Newcomer, in training
 
Member since: Feb 2009, 5 posts
The problem is I am part of the support staff and we are getting desperate to fix this. Members are irritated and tend to not come back

Googling for the error gave very few results, with techspot.com being the only useful one it seems. Our setup is exactly the same as here, vbulletin, photopost
  #8  
Old 02-17-2009
Ex-TechSpotter
 
Member since: Dec 2007, 18,354 posts
We are using vBulletin 3.7.4, the Latest Version is: 3.8.1 (although no online manual as yet for this version)
What version are you using ?
  #9  
Old 02-17-2009
Newcomer, in training
 
Member since: Feb 2009, 5 posts
We have 3.7.2.

I think we found the issue though. The invalid call to script is only a symptom of photpost failing to work with the vbulletin cookie. So we are trying to fix the domain cookies, and although everything looks alright, something is still broken. And mostly only in IE6

IE6 users get logged out when trying to vew a member gallery, and then when they log back in, it gives invalid call to script errors :S
  #10  
Old 02-17-2009
Ex-TechSpotter
 
Member since: Dec 2007, 18,354 posts
Definitely a Julio or Per (staff members) technical expertise area
You may receive a reply if they read this thread. Keep us informed. I'm pretty sure we had the same IE6 error though, which was fixed somehow
  #11  
Old 02-17-2009
Newcomer, in training
 
Member since: Feb 2009, 5 posts
Cool thanks. Ill keep checking in

I tried to pm Julio, but I need 45 posts before I can pm
  #12  
Old 02-17-2009
Ex-TechSpotter
 
Member since: Dec 2007, 18,354 posts
You don't need to PM him, as he is subscribed to this thread, therefore he will get a new reply email.

I note that you tried to PM him, before posting a reply here. Yes that failed, as not allowed
  #13  
Old 02-17-2009
Newcomer, in training
 
Member since: Feb 2009, 5 posts
Ah ok no probs.

Thanks for the replies, I appreciate it!
  #14  
Old 02-17-2009
Julio's Avatar
TechSpot Executive Editor
 
Location: Ecuador
Member since: Feb 2002, 5,352 posts
System specs
That was a rather long time ago, so I'm trying to remember what we did to fix this.

If you looked into Photopost's own forums and couldn't find an answer, I will go with the few things that come to mind considering the problem surfaced when we moved servers:

* Check PP's Folder permissions
* Upgrade both vB and PP to its latest versions
* Import a PP DB backup