Message from webmaster tools regarding incorrect rel-alternate tags

[Marcin Kalak]

Execution order changes order of plugins within the framework of a hook. Execution order does not change the order of the hooks. On our test forum this hook is working properly. vB license has no time limit, so you can do the upgrade. Your version vB has long been out of date so I recommend execution upgrade. I think that this will solve the issue, if that does not work then we'll look further.

[tavenger5]

so in 4.2 the execution order of the parse_templates hook is different?

Unfortunately updating to 4.2 is a huge task as it would break several other addons that I use.

[tavenger5]

I checked class_bootstrap.php and the parse_templates hook is in the same place in the file on both 4.1.12 and 4.2.2. Can you elaborate on what is causing the problem with that hook and it executing too early?

[Marcin Kalak]

We support the latest versions and vBET is adapted to the latest version. Each version contains a lot of changes. If you do update, and you still have this issue then we will be happy to assist you.

[tavenger5]

I'm not going to update vbulletin, and spend a lot of time doing so, unless I know that updating is going to solve the issue with the flags. You said that you "think" it will solve the issue. I need a confirmation on exactly what is causing the problem and that it WILL solve the issue.

[Marcin Kalak]

We support the latest version. VB4 is a lifetime license, so please do update. If issue will remain then we can help, because now it seems that the fault of the old, unsupported version.

[tavenger5]

We support the latest version. VB4 is a lifetime license, so please do update. If issue will remain then we can help, because now it seems that the fault of the old, unsupported version.

Okay, can you tell me what is going wrong with the old version?

[vBET]

Okay, can you tell me what is going wrong with the old version?

It is old and differed that new, and not supported, since vBET4.x is tested on newest vB4 version. When you will have newest vB4 version and issue will still exists we will gladly help you.
At this moment we can assume that there is nothing wrong with vBET since the issue cannot be reproduced on newest vB version.
There is no bug in vBET4.x - you are just using it on not compatible old vB4 version. Wrong fuel for wrong engine - no service issue, just wrong using issue.

Please update vB4 to newest vB4 version.

If there is no bug on supported vB version, we will consider this issue closed, since there is no issue with vBET, just with wrong usage and you already got solution for that.

Marcin - please close the ticket if there will be no new input in next few days (bug exists on newest vB4 version).

We already gave you the support - if you do not want to use it it is your choice. We respect our clients - we also respect that you prefer to have the issue instead of using our support which was already given.
This is not a chat room and our staff will close this ticket, since solution was already given and as for now we have confirmation that on newest vB4 version it is all OK.

Thanks for your input.
Hope that you will decide to use the support you was asking for.
It not - still thanks for understanding that there is nothing to add in this area, until you use the support instead of repeat all the time that you want support and do not use it when it is given.

Marcin will continue to support this ticket in next few days and answer only when we will have your feedback that on newest (supported) vB4 version the issue also exists. If not it will be closed.

[tavenger5]

I'm not asking you to fix the problem with an unsupported version of vBulletin. I'm asking you to tell me where the problem is, and confirm that it is, in fact, a problem with 4.1.12 so I can fix it. You've only told me that it might be a problem with 4.1.12. I need to know that it is a problem before I go out of my way to update vBulletin.

As stated, I'm not going to go through the trouble of upgrading vbulletin if I don't have to. It would cost me a considerable amount of time and money to update other custom mods. You have the login credentials for my site. It should be easy for you to tell me what is going wrong with the parse_templates hook. For example, x file is different between 4.1.12 and 4.2.2. Or parse_templates needs to execute before x hook.

I've had your product since the beginning and I just renewed my license. I would expect you would treat a long standing customer with a little more respect.

Again, all I need is to be pointed in the right direction. I'm not asking to rewrite the entire mod to work with 4.1.12. I honestly don't think this is an absurd request especially considering I am a long time customer.

[Marcin Kalak]

Our product has been adapted to the latest version of vB, it is impossible to adapt the product to all versions.