| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> |
| Cc: | Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com>, Mike Surcouf <mikes(at)surcouf(dot)co(dot)uk>, "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: Cant browse servers after update to pgadmin 1.6 (server version) |
| Date: | 2017-07-21 08:35:10 |
| Message-ID: | CA+OCxoy-oqDQocG=9+SAzrCc4gaMkObAaneS4GjmCDcSWq9zww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Wed, Jul 19, 2017 at 1:54 PM, Murtuza Zabuawala <
murtuza(dot)zabuawala(at)enterprisedb(dot)com> wrote:
>
>
> On Wed, Jul 19, 2017 at 6:16 PM, Khushboo Vashi <
> khushboo(dot)vashi(at)enterprisedb(dot)com> wrote:
>
>> On Wed, Jul 19, 2017 at 6:10 PM, Murtuza Zabuawala <
>> murtuza(dot)zabuawala(at)enterprisedb(dot)com> wrote:
>>
>>> Okay, I think this is a bug with 1.6.
>>>
>>> Found similar issue: https://redmine.postgresql.org/issues/2563
>>>
>>>
>> So, as per this RM information, you can change the WSGIScriptAlias from
>> */pgadmin4* to */* to fix this issue.
>>
>>>
>>> Yes, This is a work around.
> But we also have to fix this issue at code level to honour the virtual
> DirectoryRoot path :)
>
Are you working on this Murtuza? I don't want it to get forgotten.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Murtuza Zabuawala | 2017-07-21 08:44:44 | Re: Cant browse servers after update to pgadmin 1.6 (server version) |
| Previous Message | Dave Page | 2017-07-21 08:27:10 | Re: pgAdmin 4 v1.6 Released! |