Date: Fri, 16 Feb 2018 10:19:37 -0700 From: "Janky Jay, III" <jankyj@unfs.us> To: freebsd-ports@freebsd.org Subject: Re: mail/postfixadmin: Error Regarding "SCOPE_BUBBLE_UP". Message-ID: <2cef941d-8340-fef3-5792-47d3e6b6bd77@unfs.us> In-Reply-To: <d0d4ad5b-a3d4-963a-fa23-edd4cd0bc50f@bluerosetech.com> References: <0fcad468-5deb-f449-9847-9bb57bb1f014@unfs.us> <a3e9be78-87f5-2d88-0100-6375a988abc3@bluerosetech.com> <e2c93824-d899-565a-88d9-c5ac14818ce1@unfs.us> <7bc05025-49de-be18-8b88-7388d6df70b2@unfs.us> <d0d4ad5b-a3d4-963a-fa23-edd4cd0bc50f@bluerosetech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --CkSRc8o5zk4e3hPIoKr4HPFdMo0ABDkIM Content-Type: multipart/mixed; boundary="CGIb5P8E80HmoWFvkmIlFcraAtX60gzkE"; protected-headers="v1" From: "Janky Jay, III" <jankyj@unfs.us> To: freebsd-ports@freebsd.org Message-ID: <2cef941d-8340-fef3-5792-47d3e6b6bd77@unfs.us> Subject: Re: mail/postfixadmin: Error Regarding "SCOPE_BUBBLE_UP". References: <0fcad468-5deb-f449-9847-9bb57bb1f014@unfs.us> <a3e9be78-87f5-2d88-0100-6375a988abc3@bluerosetech.com> <e2c93824-d899-565a-88d9-c5ac14818ce1@unfs.us> <7bc05025-49de-be18-8b88-7388d6df70b2@unfs.us> <d0d4ad5b-a3d4-963a-fa23-edd4cd0bc50f@bluerosetech.com> In-Reply-To: <d0d4ad5b-a3d4-963a-fa23-edd4cd0bc50f@bluerosetech.com> --CGIb5P8E80HmoWFvkmIlFcraAtX60gzkE Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Hi Mel, On 02/16/2018 05:02 AM, Mel Pilgrim wrote: > On 2018-02-14 19:13, Janky Jay, III wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> May have spoken too soon... >> >> On 2/14/2018 7:45 PM, Janky Jay, III wrote: >>> Hello Mel, >>> >>> On 2/13/2018 7:42 AM, Mel Pilgrim wrote: >>>> (Putting on my mail/postfixadmin maintainer hat) >>> >>>> On 2018-02-11 15:24, Janky Jay, III wrote: >>>>> Hello All, >>>>> >>>>> Versions: FreeBSD - 11.1-RELEASE-p6 PostfixAdmin - 3.1 Smarty3 >>>>> - 3.1.30 >>> >>>> Postfixadmin bundles its own copy of Smarty, and in PFA 3.1 it's >>>> Smarty 3.1.29. Installing www/smarty3 isn't necessary. Are you >>>> using it for something else? >>> >>> Ah. That's very interesting. The only reason I had Smarty3 >>> installed was for PFA (must have been before it shipped with it's >>> own version, maybe?). I remember a while back I uninstalled it >>> because it was an unused leaf port and immediately PFA stopped >>> working with Smarty3 errors in the http logs. I've just removed >>> Smarty3 again and PFA seems to work just fine. I have no idea >>> what's going on anymore. :) >>> >>> Thanks a ton for the reply, though! I've got my PFA back! >>> >> >> =C2=A0=C2=A0=C2=A0=C2=A0I've removed Smarty3 and the login page presen= ts itself (and allows >> me to login) without any issue. However, attempting to view anything >> within PFA (such as virtual mailboxes or domains), I see the following= >> error(s) in the http log file: >> >> PHP Warning: >> require_once(/usr/local/share/smarty3/plugins/function.html_options.ph= p) >=20 > So something is rewriting the Smarty path from PFA's > /usr/local/www/postfixadmin/smarty/libs to what I'm guessing is the pat= h > used by the now-removed www/smarty3. >=20 > This sounds like a caching issue.=C2=A0 After removing www/smarty3, did= you: >=20 > - check there were no lingering Smarty Apache/PHP config bits in > httpd.conf, php.ini, etc.; > - restart Apache and, if applicable, the PHP module; > - delete everything in templates_c? >=20 > There aren't any configurable options that would change from where > postfixadmin includes Smarty, but the path it uses is set as SMARTY_DIR= > in smarty/libs/Autoloader.php and the correct value is ''. >=20 Thanks again for the replies. I do appreciate it. I did remove any config bits from Apache/PHP (most specifically the path to smarty3 in php.ini) and restarted Apache. However, I did not empty the "templates_c" directory (DUH!). That seems to have done the trick! Looks like PFA is back to working again. Thanks again, Mel! Regards, Janky Jay, III --CGIb5P8E80HmoWFvkmIlFcraAtX60gzkE-- --CkSRc8o5zk4e3hPIoKr4HPFdMo0ABDkIM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlqHEqkACgkQGK3MsUbJZn6hZwCfU4bpB+g2CEYY67g9ulmrWe+N YMIAn3B+Fyn65QQRhS7O61HUEiLTn3vi =z7GH -----END PGP SIGNATURE----- --CkSRc8o5zk4e3hPIoKr4HPFdMo0ABDkIM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2cef941d-8340-fef3-5792-47d3e6b6bd77>