Issue after Update to phpbb 3.3.5

[hfgdjk]

Unfortunately, after an update to phpbb 3.3.5. i can no longer create hookups. with older hookups I can no longer enter or change the entries.

I don't see any error messages, just the announcement "The forum you selected does not exist."
As I said, I'm using phpbb 3.3.5 and PHP 7.4.27.

Has anyone else seen this error and is there a solution for it?

Thank you, greetings

edit: I just noticed: the normal url for a topic is: * / phpBB / topic /385, but the forwarding after creating a hookup or after entering dates or availabilities goes to */ 385. I don't remember if this was the same case before the update.

[gn36]

The hookup doesn't mess with URLs since it is fully integrated into the existing topics.
But you seem to have an extension that does. Your URLs are not standard it seems, I am guessing you are using some sort of URL wrangling mod?
Usually, you should have an URL like example.com/path/to/phpbb/viewtopic.php?t=1234 or so, where 1234 is your Topic ID.
What I guess, happens on your Board is: That Extension that you are using is messing with the Base URL that the hookup sees and changes the URLs in a wrong way. This won't have an effect for the URLs that that extension expected, but it will have an effect for the URLs used as a target by the hookup.
The way this is currently done is: The target of the forms is the URL that you normally use to view the forum. This usually should work, since we want to display the topic again after each change. But apparently, your other extension messes with the URLs that the forum actually gets to see and as a result, the target URL is not correct. Then your browser sends the data to the wrong URL and as a result you get the message that the forum has not been found. This is likely, because there is some confusion about relative URLs due to the subfolders that your other extension puts into your URL. I've had problems with this in the past as well when I created such a system for the phpBB.de Website surrounding phpBB. We had a huge amount of problems with it because the relative URLs kept getting wrong in a similar way as you described it. You get either URLs like phpBB/topic/topic/385 (repetition of "topic") or you lack something like you described. But essentially, there is an error in the rewrite.

So to summarize: I think something is wrong with your other extension not with hookup.

To find out more, you could do a little bit of debugging in my extension, though. There is a fairly central location that generates the URL that is used as a target, running the URLs that I use through "append_sid", to allow non-cookie users to also use the hookup. I guess this is where your other extension messes up my URLs.

So if you use cookies, you could replace the following line:
$viewtopic_url = append_sid("{$this->phpbb_root_path}viewtopic.{$this->phpEx}?f=$forum_id&t=$topic_id");
inside event/viewtopic.php of the hookup extension by this one:
$viewtopic_url = "{$this->phpbb_root_path}viewtopic.{$this->phpEx}?f=$forum_id&t=$topic_id";

And as a result, your extension should no longer overwrite most of the URLs. This will exclude anyone not using cookies and not sure if this will work for everyone else, maybe you will end up with URLs like phpBB/topic/viewtopic.php?f=1234&t=5678 instead of phpBB/viewtopic.php?f=1234&t=5678 (and maybe even that works, and only breaks the graphics, who knows) but maybe it works and then at least it only doesn't work for people without cookies.

But probably, you should go to the creator of that other extension and check with him why the rewrite ends up like this.

[gn36]

Oh and obviously, you could also deactivate that other extension and see if it helps. If it does, you'll know there is nothing wrong with hookup.

[hfgdjk]

Hi,

thx for your help. First, i did your changes to the viewtopic.php, unfortunately it did not work - the error still occurs.
Secondly, i found the problem: It's the p8pbb bridge coded by alterbrains.

The bridge needs some additional code on the .htaccess in forum root:

RewriteCond %{REQUEST_FILENAME} /com(\/?)$ RewriteRule (.*) /intern [R=301,L] RewriteCond %{REQUEST_FILENAME} /com/index.php RewriteRule (.*) /intern?%{QUERY_STRING} [R=301,L] RewriteCond %{REQUEST_FILENAME} /com/ucp.php RewriteRule (.*) /intern/user?%{QUERY_STRING} [R=301,L] RewriteCond %{REQUEST_FILENAME} /com/viewforum.php RewriteRule (.*) /intern/forum?%{QUERY_STRING} [R=301,L] RewriteCond %{REQUEST_FILENAME} /com/viewtopic.php RewriteRule (.*) /intern/topic?%{QUERY_STRING} [R=301,L] RewriteCond %{REQUEST_FILENAME} /com/memberlist.php RewriteRule (.*) /intern/members?%{QUERY_STRING} [R=301,L] RewriteCond %{REQUEST_FILENAME} /com/report.php RewriteRule (.*) /intern/report?%{QUERY_STRING} [R=301,L] RewriteCond %{REQUEST_FILENAME} /com/posting.php RewriteRule (.*) /intern/post?%{QUERY_STRING} [R=301,L] RewriteCond %{REQUEST_FILENAME} /com/mcp.php RewriteRule (.*) /intern/moderator?%{QUERY_STRING} [R=301,L]

"intern" is the alias for joomla, and "com" is the folder where the forum is installed to.

If i use "com" while browsing the forum, it works. if I visit the forum via link in the menu (*/intern/blabla), the error occurs.

I posted a ticket now on author's support. I know, its not your mod/ext/whatever, but do you see anything, any suggestion?

Thx anyway, best regards. I'll keep you posted about solutions, etc.

[gn36]

Hm, it is a long time since I used rewrite rules... They are kind of hard to read the way you put them in.

I am not sure if I understand correctly how your forum/joomla is set up, but it almost looks to me like the rules are reversed from what you should have. If the files are actually in a folder called "com" and you try to access them via "intern", then I would expect a rule that rewrites from intern in the conditions to com in the target. But you seem to have it reversed from this.
So I would have expected for example something like:
RewriteRule intern/topic/([0-9]+) /com/viewtopic.php?t=$1

EDIT: Ah no, this part might be handled by phpBB itself. So these rules are probably what tells the browser where to go when it tries to use the "com" directly instead of the rewritten URLs.
But that should mean that you can no longer use the old URLs if you have these rules in place, because your browser would immediately go to the new URLs instead.
If that is the case, then maybe you want to look a bit closer at this rule:
RewriteCond %{REQUEST_FILENAME} /com/viewtopic.php RewriteRule (.*) /intern/topic?%{QUERY_STRING} [R=301,L]
But I'd do some more debugging and check what the form target is that is presented to the browser. If that already tries to target something garbage that is wrong, then the rewriting part of the ext that is inside phpBB is wrong. If that seems correct, then maybe the rewrite is wrong. But I think the error is rather in the part of that extension which manipulates "append_sid".