Frequent file juggling woes [message #6298] |
Fri, 14 April 2017 22:25  |
apmuthu
Messages: 30 Registered: April 2017 Location: Chennai Singapore
|
Member |
|
|
Files like htaccess.txt, htaccess.demo.txt are present in some releases whilst not in some previous releases. Maintaining version changes becomes cumbersome.
The following appear in one or the other release and sometimes within a single release:
htaccess.txt: php_value always_populate_raw_post_data -1
and
htaccess.demo.txt: php_value always_populate_raw_post_data 1
|
|
|
Re: Frequent file juggling woes [message #6301 is a reply to message #6298] |
Sat, 15 April 2017 00:56   |
apmuthu
Messages: 30 Registered: April 2017 Location: Chennai Singapore
|
Member |
|
|
This link has more info on the php.ini parameter value being -1.
Quote:
PHP 5.6.0 and above does not support always_populate_raw_post_data, so it need to be set to -1.
For earlier versions of PHP, use:
php_flag always_populate_raw_post_data On
or
php_flag always_populate_raw_post_data 1
[Updated on: Sat, 15 April 2017 00:56] Report message to a moderator
|
|
|
|
Re: Frequent file juggling woes [message #6846 is a reply to message #6307] |
Sun, 20 August 2017 05:16   |
apmuthu
Messages: 30 Registered: April 2017 Location: Chennai Singapore
|
Member |
|
|
Missing xample.zip in v2.05.0 release - is it no longer supported?
The documentation still refers to it.
What folder should we extract the new radicore_admin.zip into?
There is no info on this file in the documentation.
Why does the Menu SQL schema now define each string field with "COLLATE utf8_unicode_ci " although they are in the default for the ENGINE in the last line of the table definition?
Please remove all the Thumbs.db files from future releases.
[Updated on: Sun, 20 August 2017 05:26] Report message to a moderator
|
|
|
|
|
|
|
Re: Frequent file juggling woes [message #7090 is a reply to message #7089] |
Sun, 12 November 2017 09:51   |
apmuthu
Messages: 30 Registered: April 2017 Location: Chennai Singapore
|
Member |
|
|
To convert Windows CRLF line endings to Unix style LF line endings in windows use:
TYPE input_filename | MORE /P > output_filename
Create a batch file to operate on desired file extensions recursively. Make sure that the input and output files are different (use different folders when the name is the same) otherwise you will lose your source file itself with no conversion or target file being available.
An utility do this conversion in a GUI is available at the DOS2Unix page.
If any SQL statement spans more than one line especially in the middle of a long string, chances are the "^M" (CR) character will get embedded into it and cause searches to fail.
As you work entirely on windows, I would assume that all the files would have windows CRLF line endings which is not the case. There are scores of files that retain the Unix style line endings. Using the likes of NotePad++ with line endings set to Unix style will make for such editing to be consistent with webservers running linux and windows. The possible reason your linux servers have not complained is that the file transfer program used may have auto translated the line endings during upload.
The current Radicore v2.08.0 completely in unix style line endings is available on GitHub.
[Updated on: Sun, 12 November 2017 09:58] Report message to a moderator
|
|
|
|
|
|
|