Error True and Error Unexpected Token
Hello
I am having problems uploading files to the server i get the errors Error True and Unexpected token
The files dont exceed past the 3 mb so i dont think is the max execution time and upload size in the php configurations. Your help is much appreciated
Thank you
Question information
- Language:
- English Edit question
- Status:
- Expired
- For:
- Xibo Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
![]() |
#1 |
Can you submit a "report fault" file that captures the error?
Revision history for this message
![]() |
#2 |
how do i get a report fault file are you talking about taking a screenshot
of the error and sending it or is there a log in the server that i can
access because i only see the log in advance options but its not of errors.
On Wed, Oct 29, 2014 at 6:06 AM, Dan Garner <
<email address hidden>> wrote:
> Your question #256262 on Xibo changed:
> https:/
>
> Status: Open => Needs information
>
> Dan Garner requested more information:
> Can you submit a "report fault" file that captures the error?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
![]() |
#3 |
i see on the logs you can filter it out to see the type ; error and the
page : fault but it only shows me activity of the current day not of the
day of the error
On Thu, Oct 30, 2014 at 9:16 AM, SantiiSoporte <
<email address hidden>> wrote:
> Your question #256262 on Xibo changed:
> https:/
>
> Status: Needs information => Open
>
> You gave more information on the question:
> how do i get a report fault file are you talking about taking a screenshot
> of the error and sending it or is there a log in the server that i can
> access because i only see the log in advance options but its not of errors.
>
> On Wed, Oct 29, 2014 at 6:06 AM, Dan Garner <
> <email address hidden>> wrote:
>
> > Your question #256262 on Xibo changed:
> > https:/
> >
> > Status: Open => Needs information
> >
> > Dan Garner requested more information:
> > Can you submit a "report fault" file that captures the error?
> >
> > --
> > To answer this request for more information, you can either reply to
> > this email or enter your reply at the following page:
> > https:/
> >
> > You received this question notification because you asked the question.
> >
>
> --
> You received this question notification because you asked the question.
>
Revision history for this message
![]() |
#4 |
You go to Advanced -> Report Fault and follow the instructions.
Revision history for this message
![]() |
#5 |
i go to advanced and it says before you can report a fault you have to
follow the next steps and it shows the services of xibo running like php
and mysql and at the end there is an exclamation mark for large file
uploads. I dont know why this alert shows up still because i configured the
php.ini file to allow uploads bigger than 128Mb as well as execution time.
To be able to report a fault all this services need to be green right? here
are the setting of hte php.ini file that i changed
;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;
; Maximum execution time of each script, in seconds
; http://
; Note: This directive is hardcoded to 0 for the CLI SAPI
max_execution_time = 180
; Maximum amount of time each script may spend parsing request data. It's a
good
; idea to limit this time on productions servers in order to eliminate
unexpectedly
; long running scripts.
; Note: This directive is hardcoded to -1 for the CLI SAPI
; Default Value: -1 (Unlimited)
; Development Value: 60 (60 seconds)
; Production Value: 60 (60 seconds)
; http://
max_input_time = 160
; Maximum input variable nesting level
; http://
;max_input_
; Maximum amount of memory a script may consume (128MB)
; http://
memory_limit = 150MB
;;;;;;;;;;;;;;;;;
; Data Handling ;
;;;;;;;;;;;;;;;;;
; Note - track_vars is ALWAYS enabled
; The separator used in PHP generated URLs to separate arguments.
; PHP's default setting is "&".
; http://
; Example:
;arg_separator.
; List of separator(s) used by PHP to parse input URLs into variables.
; PHP's default setting is "&".
; NOTE: Every character in this directive is considered as separator!
; http://
; Example:
;arg_separator.
; This directive determines which super global arrays are registered when
PHP
; starts up. If the register_globals directive is enabled, it also
determines
; what order variables are populated into the global space. G,P,C,E & S are
; abbreviations for the following respective super globals: GET, POST,
COOKIE,
; ENV and SERVER. There is a performance penalty paid for the registration
of
; these arrays and because ENV is not as commonly used as the others, ENV is
; is not recommended on productions servers. You can still get access to
; the environment variables through getenv() should you need to.
; Default Value: "EGPCS"
; Development Value: "GPCS"
; Production Value: "GPCS";
; http://
variables_order = "GPCS"
; This directive determines which super global data (G,P,C,E & S) should
; be registered into the super global array REQUEST. If so, it also
determines
; the order in which that data is registered. The values for this directive
are
; specified in the same manner as the variables_order directive, EXCEPT one.
; Leaving this value empty will cause PHP to use the value set in the
; variables_order directive. It does not mean it will leave the super
globals
; array REQUEST empty.
; Default Value: None
; Development Value: "GP"
; Production Value: "GP"
; http://
request_order = "GP"
; Whether or not to register the EGPCS variables as global variables. You
may
; want to turn this off if you don't want to clutter your scripts' global
scope
; with user data. This makes most sense when coupled with track_vars - in
which
; case you can access all of the GPC variables through the $HTTP_*_VARS[],
; variables.
; You should do your best to write your scripts so that they do not require
; register_globals to be on; Using form variables as globals can easily
lead
; to possible security problems, if the code is not very well thought of.
; http://
rgister_globals = Off
; Determines whether the deprecated long $HTTP_*_VARS type predefined
variables
; are registered by PHP or not. As they are deprecated, we obviously don't
; recommend you use them. They are on by default for compatibility reasons
but
; they are not recommended on production servers.
; Default Value: On
; Development Value: Off
; Production Value: Off
; http://
register_
; This directive determines whether PHP registers $argv & $argc each time it
; runs. $argv contains an array of all the arguments passed to PHP when a
script
; is invoked. $argc contains an integer representing the number of arguments
; that were passed when the script was invoked. These arrays are extremely
; useful when running scripts from the command line. When this directive is
; enabled, registering these variables consumes CPU cycles and memory each
time
; a script is executed. For performance reasons, this feature should be
disabled
; on production servers.
; Note: This directive is hardcoded to On for the CLI SAPI
; Default Value: On
; Development Value: Off
; Production Value: Off
; http://
register_argc_argv = Off
; When enabled, the SERVER and ENV variables are created when they're first
; used (Just In Time) instead of when the script starts. If these variables
; are not used within a script, having this directive on will result in a
; performance gain. The PHP directives register_globals,
register_
; and register_argc_argv must be disabled for this directive to have any
affect.
; http://
auto_globals_jit = On
; Maximum size of POST data that PHP will accept.
; http://
post_max_size = 150MB
; Magic quotes are a preprocessing feature of PHP where PHP will attempt to
; escape any character sequences in GET, POST, COOKIE and ENV data which
might
; otherwise corrupt data being placed in resources such as databases before
; making that data available to you. Because of character encoding issues
and
; non-standard SQL implementations across many databases, it's not currently
; possible for this feature to be 100% accurate. PHP's default behavior is
to
; enable the feature. We strongly recommend you use the escaping mechanisms
; designed specifically for the database your using instead of relying on
this
; feature. Also note, this feature has been deprecated as of PHP 5.3.0 and
is
; scheduled for removal in PHP 6.
; Default Value: On
; Development Value: Off
; Production Value: Off
; http://
magic_quotes_gpc = Off
; Magic quotes for runtime-generated data, e.g. data from SQL, from exec(),
etc.
; http://
magic_quotes_
; Use Sybase-style magic quotes (escape ' with '' instead of \').
; http://
magic_quotes_sybase = Off
; Automatically add files before PHP document.
; http://
auto_prepend_file =
; Automatically add files after PHP document.
; http://
auto_append_file =
; By default, PHP will output a character encoding using
; the Content-type: header. To disable sending of the charset, simply
; set it to be empty.
; PHP's built-in default is text/html
; http://
default_mimetype = "text/html"
; PHP's default character set is set to empty.
; http://
;default_charset = "iso-8859-1"
; Always populate the $HTTP_RAW_POST_DATA variable. PHP's default behavior
is
; to disable this feature.
; http://
;always_
;;;;;;;;;;;;;;;
; File Uploads ;
;;;;;;;;;;;;;;;;
; Whether to allow HTTP file uploads.
; http://
file_uploads = On
; Temporary directory for HTTP uploaded files (will use system default if
not
; specified).
; http://
upload_tmp_dir = "c:/wamp/tmp"
; Maximum allowed size for uploaded files.
; http://
upload_max_filesize = 150MB
On Fri, Oct 31, 2014 at 11:26 AM, Dan Garner <
<email address hidden>> wrote:
> Your question #256262 on Xibo changed:
> https:/
>
> Status: Open => Needs information
>
> Dan Garner requested more information:
> You go to Advanced -> Report Fault and follow the instructions.
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
![]() |
#6 |
Sorry theres is one more thing i dont know if this is related to changing
the php.ini file but my Log in advanced is no longer viewable it says
error getting record
On Tue, Nov 4, 2014 at 10:08 AM, Santiago Segovia <
<email address hidden>> wrote:
> i go to advanced and it says before you can report a fault you have to
> follow the next steps and it shows the services of xibo running like php
> and mysql and at the end there is an exclamation mark for large file
> uploads. I dont know why this alert shows up still because i configured the
> php.ini file to allow uploads bigger than 128Mb as well as execution time.
> To be able to report a fault all this services need to be green right? here
> are the setting of hte php.ini file that i changed
>
> ;;;;;;;;;;;;;;;;;
> ; Resource Limits ;
> ;;;;;;;;;;;;;;;;;;
> ; Maximum execution time of each script, in seconds
> ; http://
> ; Note: This directive is hardcoded to 0 for the CLI SAPI
> max_execution_time = 180
> ; Maximum amount of time each script may spend parsing request data. It's
> a good
> ; idea to limit this time on productions servers in order to eliminate
> unexpectedly
> ; long running scripts.
> ; Note: This directive is hardcoded to -1 for the CLI SAPI
> ; Default Value: -1 (Unlimited)
> ; Development Value: 60 (60 seconds)
> ; Production Value: 60 (60 seconds)
> ; http://
> max_input_time = 160
> ; Maximum input variable nesting level
> ; http://
> ;max_input_
> ; Maximum amount of memory a script may consume (128MB)
> ; http://
> memory_limit = 150MB
> ;;;;;;;;;;;;;;;;;
> ; Data Handling ;
> ;;;;;;;;;;;;;;;;;
> ; Note - track_vars is ALWAYS enabled
> ; The separator used in PHP generated URLs to separate arguments.
> ; PHP's default setting is "&".
> ; http://
> ; Example:
> ;arg_separator.
> ; List of separator(s) used by PHP to parse input URLs into variables.
> ; PHP's default setting is "&".
> ; NOTE: Every character in this directive is considered as separator!
> ; http://
> ; Example:
> ;arg_separator.
> ; This directive determines which super global arrays are registered when
> PHP
> ; starts up. If the register_globals directive is enabled, it also
> determines
> ; what order variables are populated into the global space. G,P,C,E & S are
> ; abbreviations for the following respective super globals: GET, POST,
> COOKIE,
> ; ENV and SERVER. There is a performance penalty paid for the registration
> of
> ; these arrays and because ENV is not as commonly used as the others, ENV
> is
> ; is not recommended on productions servers. You can still get access to
> ; the environment variables through getenv() should you need to.
> ; Default Value: "EGPCS"
> ; Development Value: "GPCS"
> ; Production Value: "GPCS";
> ; http://
> variables_order = "GPCS"
> ; This directive determines which super global data (G,P,C,E & S) should
> ; be registered into the super global array REQUEST. If so, it also
> determines
> ; the order in which that data is registered. The values for this
> directive are
> ; specified in the same manner as the variables_order directive, EXCEPT
> one.
> ; Leaving this value empty will cause PHP to use the value set in the
> ; variables_order directive. It does not mean it will leave the super
> globals
> ; array REQUEST empty.
> ; Default Value: None
> ; Development Value: "GP"
> ; Production Value: "GP"
> ; http://
> request_order = "GP"
> ; Whether or not to register the EGPCS variables as global variables. You
> may
> ; want to turn this off if you don't want to clutter your scripts' global
> scope
> ; with user data. This makes most sense when coupled with track_vars - in
> which
> ; case you can access all of the GPC variables through the $HTTP_*_VARS[],
> ; variables.
> ; You should do your best to write your scripts so that they do not require
> ; register_globals to be on; Using form variables as globals can easily
> lead
> ; to possible security problems, if the code is not very well thought of.
> ; http://
> rgister_globals = Off
> ; Determines whether the deprecated long $HTTP_*_VARS type predefined
> variables
> ; are registered by PHP or not. As they are deprecated, we obviously don't
> ; recommend you use them. They are on by default for compatibility reasons
> but
> ; they are not recommended on production servers.
> ; Default Value: On
> ; Development Value: Off
> ; Production Value: Off
> ; http://
> register_
> ; This directive determines whether PHP registers $argv & $argc each time
> it
> ; runs. $argv contains an array of all the arguments passed to PHP when a
> script
> ; is invoked. $argc contains an integer representing the number of
> arguments
> ; that were passed when the script was invoked. These arrays are extremely
> ; useful when running scripts from the command line. When this directive is
> ; enabled, registering these variables consumes CPU cycles and memory each
> time
> ; a script is executed. For performance reasons, this feature should be
> disabled
> ; on production servers.
> ; Note: This directive is hardcoded to On for the CLI SAPI
> ; Default Value: On
> ; Development Value: Off
> ; Production Value: Off
> ; http://
> register_argc_argv = Off
> ; When enabled, the SERVER and ENV variables are created when they're first
> ; used (Just In Time) instead of when the script starts. If these variables
> ; are not used within a script, having this directive on will result in a
> ; performance gain. The PHP directives register_globals,
> register_
> ; and register_argc_argv must be disabled for this directive to have any
> affect.
> ; http://
> auto_globals_jit = On
> ; Maximum size of POST data that PHP will accept.
> ; http://
> post_max_size = 150MB
> ; Magic quotes are a preprocessing feature of PHP where PHP will attempt to
> ; escape any character sequences in GET, POST, COOKIE and ENV data which
> might
> ; otherwise corrupt data being placed in resources such as databases before
> ; making that data available to you. Because of character encoding issues
> and
> ; non-standard SQL implementations across many databases, it's not
> currently
> ; possible for this feature to be 100% accurate. PHP's default behavior is
> to
> ; enable the feature. We strongly recommend you use the escaping mechanisms
> ; designed specifically for the database your using instead of relying on
> this
> ; feature. Also note, this feature has been deprecated as of PHP 5.3.0 and
> is
> ; scheduled for removal in PHP 6.
> ; Default Value: On
> ; Development Value: Off
> ; Production Value: Off
> ; http://
> magic_quotes_gpc = Off
> ; Magic quotes for runtime-generated data, e.g. data from SQL, from
> exec(), etc.
> ; http://
> magic_quotes_
> ; Use Sybase-style magic quotes (escape ' with '' instead of \').
> ; http://
> magic_quotes_sybase = Off
> ; Automatically add files before PHP document.
> ; http://
> auto_prepend_file =
> ; Automatically add files after PHP document.
> ; http://
> auto_append_file =
> ; By default, PHP will output a character encoding using
> ; the Content-type: header. To disable sending of the charset, simply
> ; set it to be empty.
> ; PHP's built-in default is text/html
> ; http://
> default_mimetype = "text/html"
> ; PHP's default character set is set to empty.
> ; http://
> ;default_charset = "iso-8859-1"
> ; Always populate the $HTTP_RAW_POST_DATA variable. PHP's default behavior
> is
> ; to disable this feature.
> ; http://
> ;always_
>
> ;;;;;;;;;;;;;;;
> ; File Uploads ;
> ;;;;;;;;;;;;;;;;
>
> ; Whether to allow HTTP file uploads.
> ; http://
> file_uploads = On
>
> ; Temporary directory for HTTP uploaded files (will use system default if
> not
> ; specified).
> ; http://
> upload_tmp_dir = "c:/wamp/tmp"
>
> ; Maximum allowed size for uploaded files.
> ; http://
> upload_max_filesize = 150MB
>
> On Fri, Oct 31, 2014 at 11:26 AM, Dan Garner <
> <email address hidden>> wrote:
>
>> Your question #256262 on Xibo changed:
>> https:/
>>
>> Status: Open => Needs information
>>
>> Dan Garner requested more information:
>> You go to Advanced -> Report Fault and follow the instructions.
>>
>> --
>> To answer this request for more information, you can either reply to
>> this email or enter your reply at the following page:
>> https:/
>>
>> You received this question notification because you asked the question.
>>
>
>
Revision history for this message
![]() |
#7 |
You need to restart your webserver process before changes to PHP are picked
up in most configurations
Revision history for this message
![]() |
#8 |
we did restart the webserver through the wamp control panel we did a
restart and it still shows up the problem with the large file uploads and
the log cant be seen
On Tue, Nov 4, 2014 at 10:16 AM, Alex Harrington <
<email address hidden>> wrote:
> Your question #256262 on Xibo changed:
> https:/
>
> Status: Open => Answered
>
> Alex Harrington proposed the following answer:
> You need to restart your webserver process before changes to PHP are picked
> up in most configurations
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
![]() |
#9 |
If Large File Uploads is not green in the report fault wizard then you do have something wrong in your PHP.INI file. I would suggest that you could have a look around on google for instructions on how to update that file (that file is not specific to Xibo).
Once you have the large file uploads reporting green, if you still have the problem we can get a report fault file and try to help further.
Thanks,
Dan
Revision history for this message
![]() |
#10 |
Hello Dan
We already figured out how to bypass the problem. There was a problem in
the connection that didnt allow us to upload videos. I no longer have the
problem with the php.ini file but i would like to know how to clean the
server of accumulated files like logs and multimedia. When i go to
administrador>
and media in the library but when i try and do a backup it says i have over
40 gigs of files to backup. Is there a way to do a deep cleanse of the
server without just deleting the content in Xibo Library
Thanks
On Wed, Nov 5, 2014 at 12:56 PM, Dan Garner <
<email address hidden>> wrote:
> Your question #256262 on Xibo changed:
> https:/
>
> Status: Open => Answered
>
> Dan Garner proposed the following answer:
> If Large File Uploads is not green in the report fault wizard then you
> do have something wrong in your PHP.INI file. I would suggest that you
> could have a look around on google for instructions on how to update
> that file (that file is not specific to Xibo).
>
> Once you have the large file uploads reporting green, if you still have
> the problem we can get a report fault file and try to help further.
>
> Thanks,
> Dan
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
![]() |
#11 |
Can you let us know what you did to fix the problem? It might be useful for others with the same issues... Thanks.
Regarding Tidy up - can you try the "Tidy Library" function in Administration -> Settings.
Revision history for this message
![]() |
#12 |
we set up the connection with VPN as far as i understood like changing the
gateway
i dont have the options tidy library i have xibo 1.6.0 and i dont see that
option in administration > settings
On Tue, Nov 11, 2014 at 6:56 AM, Dan Garner <
<email address hidden>> wrote:
> Your question #256262 on Xibo changed:
> https:/
>
> Status: Open => Needs information
>
> Dan Garner requested more information:
> Can you let us know what you did to fix the problem? It might be useful
> for others with the same issues... Thanks.
>
> Regarding Tidy up - can you try the "Tidy Library" function in
> Administration -> Settings.
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
>
Revision history for this message
![]() |
#13 |
This question was expired because it remained in the 'Open' state without activity for the last 15 days.