laravel4-datatables-package icon indicating copy to clipboard operation
laravel4-datatables-package copied to clipboard

ERR_EMPTY_RESPONSE since rev #7cc0be6 (rev #7ea3200 is ok)

Open prigal opened this issue 11 years ago • 7 comments

Hi,

Just update my project today and I had an net::ERR_EMPTY_RESPONSE.

I was in rev 094ae36 before my update to lastest rev. Then I had this error and I started testing each commit since 094ae36. The bug occurs when I checkout 7cc0be6.

Request URL : http://www.domain.com/admin/sales/data?sEcho=1&iColumns=13&sColumns=%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C%2C&iDisplayStart=0&iDisplayLength=10&mDataProp_0=0&sSearch_0=&bRegex_0=false&bSearchable_0=true&bSortable_0=true&mDataProp_1=1&sSearch_1=&bRegex_1=false&bSearchable_1=true&bSortable_1=true&mDataProp_2=2&sSearch_2=&bRegex_2=false&bSearchable_2=true&bSortable_2=true&mDataProp_3=3&sSearch_3=&bRegex_3=false&bSearchable_3=true&bSortable_3=true&mDataProp_4=4&sSearch_4=&bRegex_4=false&bSearchable_4=true&bSortable_4=true&mDataProp_5=5&sSearch_5=&bRegex_5=false&bSearchable_5=true&bSortable_5=true&mDataProp_6=6&sSearch_6=&bRegex_6=false&bSearchable_6=true&bSortable_6=true&mDataProp_7=7&sSearch_7=&bRegex_7=false&bSearchable_7=true&bSortable_7=true&mDataProp_8=8&sSearch_8=&bRegex_8=false&bSearchable_8=true&bSortable_8=true&mDataProp_9=9&sSearch_9=&bRegex_9=false&bSearchable_9=true&bSortable_9=true&mDataProp_10=10&sSearch_10=&bRegex_10=false&bSearchable_10=true&bSortable_10=true&mDataProp_11=11&sSearch_11=&bRegex_11=false&bSearchable_11=true&bSortable_11=true&mDataProp_12=12&sSearch_12=&bRegex_12=false&bSearchable_12=true&bSortable_12=true&sSearch=&bRegex=false&iSortCol_0=6&sSortDir_0=desc&iSortingCols=1&_=1411848877536

prigal avatar Sep 27 '14 21:09 prigal

Phazei made some big changes lately, so we expected that somebody may find some incompatibility issues, and you found one... Hopefully Phazei can answer this faster than me, but I'll try to work on this too.

ktunkiewicz avatar Sep 29 '14 06:09 ktunkiewicz

I've ran into the same issue. This is the error that was logged:

[2014-09-30 11:30:45] local.ERROR: exception 'Symfony\Component\Debug\Exception\FatalErrorException' with message 'Can't use method return value in write context' in C:\...\vendor\bllim\datatables\src\Bllim\Datatables\Datatables.php:911
Stack trace:
#0 [internal function]: Illuminate\Exception\Handler->handleShutdown()
#1 {main} [] []

That refers to this if statement:

 if (isset($table[1]) && !empty($this->databasePrefix()) && strpos($table[1], $this->databasePrefix()) == 0) {
        $names[] = preg_replace('/^'.$this->databasePrefix().'/', '', $table[1]);
}

I'm running PHP 5.4. According to PHPStorm these kind of arbitrary expressions are only allowed in 5.5.

FrankPeters avatar Sep 30 '14 09:09 FrankPeters

i also have same issue last 7 days Request URL:http://localhost:8000/admin/users/data?sEcho=1&iColumns=5&sColumns=&iDisplayStart=0&iDisplayLength=10&mDataProp_0=0&mDataProp_1=1&mDataProp_2=2&mDataProp_3=3&mDataProp_4=4&sSearch=&bRegex=false&sSearch_0=&bRegex_0=false&bSearchable_0=true&sSearch_1=&bRegex_1=false&bSearchable_1=true&sSearch_2=&bRegex_2=false&bSearchable_2=true&sSearch_3=&bRegex_3=false&bSearchable_3=true&sSearch_4=&bRegex_4=false&bSearchable_4=true&iSortCol_0=0&sSortDir_0=asc&iSortingCols=1&bSortable_0=true&bSortable_1=true&bSortable_2=true&bSortable_3=true&bSortable_4=true&_=1412835768921

any work aroud

hassanjamal avatar Oct 09 '14 06:10 hassanjamal

Temporary workaround : go back to last working rev.

In your composer.json :

    "require": {
            ....
            "bllim/datatables": "dev-master#7ea3200bb45af3b02affcfdb30e8bea6b16381e4",
            ....
        }

prigal avatar Oct 09 '14 07:10 prigal

@pierrerigal thanks a lot . I did it after going through your details


(rev #7ea3200 is ok)


I was totally stuck as 3 of my ongoing project uses this package . Once again THANKS A LOT :+1:

hassanjamal avatar Oct 09 '14 07:10 hassanjamal

Looking into it. Also, in #162 53dbb3d the fullDataSupport was properly disabled by default, that probably caused the initial reported issue.

phazei avatar Oct 14 '14 00:10 phazei

Just submitted a pull request that should resolve the issue @FrankPeters noted.

phazei avatar Oct 14 '14 01:10 phazei