| From: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org>, Fahar Abbas <fahar(dot)abbas(at)enterprisedb(dot)com> |
| Cc: | Avin Kavish <avinkavish(at)gmail(dot)com>, Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>, Wh isere <whisere(at)gmail(dot)com>, Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>, Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com>, "pgadmin-support lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: import upload file to pgadmin get CSRF error |
| Date: | 2019-08-09 10:07:20 |
| Message-ID: | 3adc15c862289589983481002c11baaa56ecc637.camel@gunduz.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Hi,
On Tue, 2019-08-06 at 09:02 +0100, Dave Page wrote:
> My second guess is that config.py has been directly edited on the server so
> when the RPMs were upgraded, the original config.py wasn't replaced, thus
> pgAdmin is reporting the version number from the previous version (the
> version number is defined in config.py).
This cannot happen -- I did not mark config.py as a "configuration file" in the
spec file.
Regards,
--
Devrim Gündüz
Open Source Solution Architect, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim Gündüz | 2019-08-09 10:08:02 | Re: import upload file to pgadmin get CSRF error |
| Previous Message | Devrim Gündüz | 2019-08-09 10:05:48 | Re: import upload file to pgadmin get CSRF error |