Would please try to clear the cache?

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company
<http://www.enterprisedb.com>


*http://www.linkedin.com/in/asheshvashi*
<http://www.linkedin.com/in/asheshvashi>


On Tue, Aug 6, 2019 at 10:47 AM Wh isere <whis...@gmail.com> wrote:

> I run 'yum update pgadmin4' it appears pgadmin4 already 4.11, but on the
> web interface under about it still shows 4.8. Any idea? Thanks.
>
> On Tue, Aug 6, 2019 at 3:08 PM Wh isere <whis...@gmail.com> wrote:
>
>> Hello, we have updated pgadmin4 to 4.11 but this problem is still there.
>> Thanks.
>>
>> On Fri, Jun 28, 2019 at 3:09 PM Murtuza Zabuawala <
>> murtuza.zabuaw...@enterprisedb.com> wrote:
>>
>>>
>>> On Fri, Jun 28, 2019 at 10:18 AM Where is Where <whis...@gmail.com>
>>> wrote:
>>>
>>>> Thanks for the clarification Murtuza.  Any idea about when it might be,
>>>> eg the packages in here:
>>>> https://download.postgresql.org/pub/repos/yum/10/redhat/rhel-7Server-x86_64/
>>>> . Thanks!
>>>>
>>>
>>> Not sure, that is something handled by Postgres packaging community and
>>> not by pgAdmin4 team.
>>>
>>> -- Murtuza
>>>
>>>
>>>
>>>>
>>>> On Fri, Jun 28, 2019 at 1:55 PM Murtuza Zabuawala <
>>>> murtuza.zabuaw...@enterprisedb.com> wrote:
>>>>
>>>>> On Fri, Jun 28, 2019 at 6:31 AM Where is Where <whis...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Is there a way to apply this bug fix on a installation on redhat?The
>>>>>> 4.9 redhat yum package is not available yet. Thanks!
>>>>>>
>>>>>
>>>>> No, Release version of JS files are bundled by webpacker, so it is not
>>>>> feasible to patch them.
>>>>> You have to wait until the yum repo gets the updated version.
>>>>>
>>>>>
>>>>> -- Murtuza
>>>>>
>>>>>>
>>>>>> On Tue, Jun 25, 2019 at 9:30 AM Where is Where <whis...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Thank you! I will wait for the release on Thursday. Will the redhat
>>>>>>> yum package be updated too? Or can I download the tar file and use some
>>>>>>> file from it to replace the file on the server?
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> On Mon, Jun 24, 2019 at 4:25 PM Khushboo Vashi <
>>>>>>> khushboo.va...@enterprisedb.com> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Jun 24, 2019 at 11:42 AM Where is Where <whis...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thank you! I just saw that too. I tried to apply that diff only:
>>>>>>>>> https://redmine.postgresql.org/projects/pgadmin4/repository/revisions/08b78fb6a11283731cdf59d2a29fdc75e459582e/diff/web/pgadmin/misc/file_manager/static/js/utility.js
>>>>>>>>> But it doesn't seem to fix the problem.
>>>>>>>>>
>>>>>>>>> It will require bundling of the static files after applying the
>>>>>>>> patch.
>>>>>>>> Instead, you can install the pgAdmin from the nightly builds having
>>>>>>>> the latest code.
>>>>>>>>
>>>>>>>> https://www.postgresql.org/ftp/pgadmin/pgadmin4/snapshots/2019-06-24/
>>>>>>>>
>>>>>>>> *          // We need to append our csrf token with dropzone's ajax 
>>>>>>>> request header
>>>>>>>>> *
>>>>>>>>>
>>>>>>>>> *          let csrfToken = {};
>>>>>>>>> *
>>>>>>>>>
>>>>>>>>> *          csrfToken[pgAdmin.csrf_token_header] = pgAdmin.csrf_token;
>>>>>>>>> *
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>           $('div#multiple-uploads').dropzone({
>>>>>>>>>
>>>>>>>>>             paramName: 'newfile',
>>>>>>>>>
>>>>>>>>>             url: pgAdmin.FileUtils.fileConnector,
>>>>>>>>>
>>>>>>>>>             *headers: csrfToken,*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks, Junran
>>>>>>>>>
>>>>>>>>> On Mon, Jun 24, 2019 at 3:47 PM Khushboo Vashi <
>>>>>>>>> khushboo.va...@enterprisedb.com> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Jun 24, 2019 at 11:13 AM Where is Where <
>>>>>>>>>> whis...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hello, we are trying to import csv file to database from
>>>>>>>>>>> pgadmin, but when uploading file it reports '
>>>>>>>>>>> 400 Bad Request <h1>Bad Request</h1> <p>The CSRF token is
>>>>>>>>>>> missing.</p> '
>>>>>>>>>>> I looked at config.py but can't find any related setting.
>>>>>>>>>>> Any idea is much appreciated.
>>>>>>>>>>>
>>>>>>>>>>> This issue has already been reported and fixed. (Ref:
>>>>>>>>>> https://redmine.postgresql.org/issues/4350)
>>>>>>>>>> You will get the fix in the upcoming release which is scheduled
>>>>>>>>>> on coming Thursday.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Khushboo
>>>>>>>>>>
>>>>>>>>>

Reply via email to