Problem with @vendor_extension value

[Sanborn]

Support Request Template
What version of phpBB are you using? phpBB 3.1.7-pl1
What is your board's URL? http://phpbb.jack-nicholson.info
Who do you host your board with? PCExtreme
How did you install your board? I used the download package from phpBB.com
What is the most recent action performed on your board? Update from a previous version of phpBB3
Is registration required to reproduce this issue? No
Do you have any MODs installed? No
Do you have any extensions installed? Yes
What version of phpBB3 did you update from? phpBB 3.1.6
What extensions do you have installed? Advanced BBCode Box 3.1.0
Auto Database Backup 1.1.0
Board Announcements 1.0.4
External Links Open in New Window 1.0.0
Google Analytics 1.0.1
Posting Template 1.0.0
Precise Similar Topics 1.3.1-dev
User Merge 1.0.0
What styles do you currently have installed? SE Square Left
What language(s) is your board currently using? Dutch
Which database type/version are you using? MySQL 5
What is your level of experience? Comfortable with PHP and phpBB
What actions did you take (updating your board; installing a MOD, style or extension; etc.) prior to this problem becoming noticeable? Updated from phpBB 3.1.6 to phpBB 3.1.7-pl1 using the official guide from phpbb.com.
Please describe your problem. All extensions seem to have a problem using the @vendor_extension path.
E.g. (you can see this in the source) the boardannouncements extension is referring the .css and .js resources as:

/home/vhosting/g/vhost0006844/domains/jack-nicholson.info/htdocs/phpbb/ext/phpbb/boardannouncements/styles/all/theme/boardannouncements.css?assets_version=83

while this should be:

/ext/phpbb/boardannouncements/styles/all/theme/boardannouncements.css?assets_version=83

So the entire first part up to /ext should not be there.
All extensions seem to face this problem, so it's not related to one specific extension.

Note: running PHP 5.3
Also see phpinfo for more info:
http://phpbb.jack-nicholson.info/phpinfo.php
Generated by SRT Generator

[david63]

My first guess would be that there is a problem with something in the vendor folder. I would try reuploading the vendor folder from a fresh download.

[RMcGirr83]

David beat me to it.

[cprgolds]

You might also try toggling the setting in the ACP:

ACP > Server Config > Server Settings > Enable URL Rewriting and see if that helps.

[Sanborn]

Thank you for the quick feedbacks

You might also try toggling the setting in the ACP:

ACP > Server Config > Server Settings > Enable URL Rewriting and see if that helps.

Setting was configured to "No". I've now configured it to "Yes" and did a cache purge, but without success.
Problem is still there.

My first guess would be that there is a problem with something in the vendor folder. I would try reuploading the vendor folder from a fresh download.

I've downloaded a fresh full copy of phpBB 3.1.7-pl1, removed my entire "vendor" folder from the server, and uploaded the "vendor" folder from the fresh copy. Then did a cache purge, but without success.
Problem is still there.

[david63]

Is this actually a problem in that the extensions are not working?

I don't suppose you know - but were they like this before the update?

[Sanborn]

Is this actually a problem in that the extensions are not working?

I don't suppose you know - but were they like this before the update?

If I take eg the boardannouncements, then the announcement shows up (the yellow block on top), but the styling is missing (which is in the .css file).

If I take eg the Advanced BBCode Box 3.1.0, then the toolbar is showing up, but as the default one, and buttons are not working.

I turned off registration, so you can't see, but I took some screenshots to illustrate:

Screenshot (wrong toolbar and not working):


Screenshot (correct toolbar in 3.1.6, and working):



I'm wondering if, as a last resort, I could disable/delete data for all extensions, then remove all files from phpbb (so the entire forum) from the server, upload a fresh copy for 3.1.7-pl1 ?

Then I would have the upgraded database from before (in 3.1.7-pl1 version), and fresh files. I could then re-add the extensions to have them again as well?

It's some work, but if that could work it's probably easier than figuring out what went wrong with the @vendor_extension value?

[Sanborn]

A quick update:

I managed to narrow it down to the "twig" folder from the update.

I did a step by step for the upgrade process to see where it went wrong exactly.
The boards announcements extension remains visible at all times (even when the board is closed during the update). So that's an easy target to verify if the @vendor_extension path is still working (if the announcement has a correct layout, then the path is still OK).

I switched my focus to 3.1.8 now, since that's the latest version.

Steps and results:
1/ I start with the old (and working) version of my phpbb forum (3.1.6) ---> everything OK
2/ I upload the install folder for the 3.1.8 version --> everything still OK
3/ I upload the vendor/symfony folder from the 3.1.8 update (so overwriting the old one) ---> everything still OK
4/ I upload the vendor/twig folder from the 3.1.8 update (so overwriting the old one) ---> layout is broken


So there's something with the twig folder that breaks the @vendor_extension value on my end, but I don't know what. If I compare the old and new twig folder, I have 111 files that are changed, so I don't know where to start. Is the @vendor_extension value defined somewhere in the twig folder?

[david63]

Is the @vendor_extension value defined somewhere in the twig folder?

I cannot say categorically but I believe that the @vendor_extension is a phpBB definition and not specifically Twig.

The strange thing here is that I literally have dozens of extension on my test board (and some on my live board) that use this convention without any problem and this is the first time that I have heard of this problem.

I am starting to think that it may be something either on your site and/or possibly your server configuration but I do not have a clue where to start looking.

I would suggest that you post this in the Bug Tracker - not that is necessarily a bug but at least that way one of the devs will see it may be able to offer some advice.