Zeruell / ppx-raidplaner

Automatically exported from code.google.com/p/ppx-raidplaner
0 stars 0 forks source link

Re-opened Unable to log in after update (SyntaxError: Unexpected token <") #74

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I have reopened my previous ticket as it was completed as "Done" but without 
testing on my end with Drupal.

What steps will reproduce the problem?
1. Updated from Beta 0.9.8 to 1.0.0
2. Backed up directory (calendar)
3. Deleted calendar directory
4. Moved 1.0.0 files to calendar directory
5. I moved my lib/config from 0.9.8a backup to 1.0.0
6. http//website/calendar/update
7. Updated & also Repaired Database
8. Attempting to log in to raid calendar gives me an error popup. 

"A request returned an error.

SyntaxError: Unexpected token <"

What version of the product are you using? Which browser / php version are
you using?
1.0.0 / Chrome / 5.3

Additional Info:
I have tried the fix posted here and unable to log in.  I have also changed my 
php.ini to display_errors = Off

I need some more info about that.
1. Do you log in with a local user or with a user from an external binding?  
(Yes)

2. If external, which binding (e.g. Phpbb)?  : Drupal (all options are the same 
and selected in the bindings - unchanged)

3. I need the content of the last messagehub.php result - see 
https://code.google.com/p/ppx-raidplaner/wiki/DetailedBugReports

Form Data
Login:project
Action:query_credentials

Response Header
Cache-Control:no-cache, max-age=0, s-maxage=0
Connection:Keep-Alive
Content-Type:application/json
Date:Mon, 21 Oct 2013 19:44:37 GMT
Expires:Thu, 19 Nov 1981 08:52:00 GMT
Keep-Alive:timeout=5, max=58
Pragma:no-cache
Server:Apache
Transfer-Encoding:chunked

No console Errors
==================

Original issue reported on code.google.com by try...@gmail.com on 21 Oct 2013 at 7:47

GoogleCodeExporter commented 9 years ago
Binding User / Not local

Original comment by try...@gmail.com on 21 Oct 2013 at 7:48

GoogleCodeExporter commented 9 years ago
Merged with Issue 72 (duplicate) and reopened Issue 72.
Please post answers to the original message, so information does not get 
scattered.

If the problem persists, I will need the contents of the last messagehub.php 
xhr again, as there is probably a second problem (or the fix did not work in 
your case).

Original comment by arne.cl...@gmail.com on 21 Oct 2013 at 9:53