search

bgame-hunter / temars-eve-api

Automatically exported from code.google.com/p/temars-eve-api
0 stars 0 forks source link

Fatal Error in Rule creation #53

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
TEA Version? 1.2.0

SMF Version? 2.0

What steps will reproduce the problem?
1. Adding a new rule to be corp specific. Regardless off and/or/is
2. Adding new rule to an existing group
3.

What is the expected output? What do you see instead?
Expected output is new rule creations. Output instead is :

Fatal error: Uncaught exception 'Exception' with message 'String could not be 
parsed as XML' in /home/zedtemp/public_html/forum/Sources/TEA.php:1629 Stack 
trace: #0 /home/zedtemp/public_html/forum/Sources/TEA.php(1629): 
SimpleXMLElement->__construct('') #1 
/home/zedtemp/public_html/forum/Sources/TEA.php(1276): 
TEA->settings_rules('http://www.zed....') #2 
/home/zedtemp/public_html/forum/Sources/TEA.php(2732): 
TEA->Settings('http://www.zed....') #3 
/home/zedtemp/public_html/forum/Sources/Admin.php(517): ModifyTEASettings() #4 
[internal function]: AdminMain() #5 
/home/zedtemp/public_html/forum/index.php(151): call_user_func('AdminMain') #6 
{main} thrown in /home/zedtemp/public_html/forum/Sources/TEA.php on line 1629

Please provide any additional information below.
had issues with 'get character' button but resolved with chmod 644 fix.

Original issue reported on code.google.com by johnloom...@gmail.com on 15 Jun 2011 at 12:27

GoogleCodeExporter commented 8 years ago 
what corp?
I recently fixed a similar issue only was under profile
but was in relation to getting a corp xml
turned out it was bad letters in the corp description that breaks xml
and I do plan to make a fix for this but for now would like to confirm this is 
the case for you

Original comment by tema...@googlemail.com on 15 Jul 2011 at 9:10

GoogleCodeExporter commented 8 years ago 
I'm seeing this with my corp also in TEA 1.2.1 and 1.3.0 r169 running on SMF 
2.0.2.  My corp name has spaces and rule creation is successful with a corp w/ 
no spaces (e.g. "Perkone").  

I worked around this (until it's patched) by replacing the spaces with %20 
though you could also just look up your corp's ID via the character sheet API 
call.

Original comment by gvi...@gmail.com on 22 Aug 2012 at 9:45