Vbulleting 4.7 + VBSEO 3.6

[vBET]

1.) Not relevant. Not at all. And brings us nowhere. Also when you installed vbseo you had to manipulate physical files - .htaccess - still it is not relevant at all here. Also please note that vbseo code changes are forced by vbseo team which refuses to add hooks in their code which would allow to plugin vBET functionality. So please give your complains to vbseo team which by their mod architecture and by their politics (we publically asked them for hooks ant it was refused) - in other words you can thanks vbseo team for that. We realize what code changes means - why are you even write it to us? We already told you - you have full right to refuse integration and to accept potential issues with links and redirects and that you will not have translated URLs. vBET is great software which uses all possibilities to make our users live easier - proof: if you will use vBulletin Friendly URLs instead of vbseo you will have to do NO CHANGES AT ALL. It is because vBulletin made it in great way which allows to expand - vbseo made it in crappy way and they shake their asses in fear every time someone ask them to allow for expansions. Address your complains to vbseo team. This discussion has no sense and takes us nowhere. We are here to help you with your issues - please go back to issue. If issue do not exists anymore we will set it solved.
2.) I do not know your akamai CDN services or where do you have re-writes. I can guess that you have it in .htaccess or in vbseo - what would mean that you had to do it first in third party to meet requirements of other plugins... Please stop it - it doesn't have any sense. Do you have an issue or not? Configuration of your environment is normal administration task. You made it before and you will made it again. And each time you made it to meet some requirements - not for pleasure, so why you act now like you do something extraordinary? It is normal thing to configure your environment. More dependencies more effort and so on... Nice chit chat giving us nothing, so I propose to close it

We suggest to use test forum or to disable vBET for waiting time if you have some critical issues which cannot wait. About all other issues - please open new thread per new issue.

Ok - we have confirmation that the issue is solved. If the issue will go back then please write here we will gladly help you

[techanalyst]

1.) Not relevant. Not at all. And brings us nowhere. Also when you installed vbseo you had to manipulate physical files - .htaccess - still it is not relevant at all here. Also please note that vbseo code changes are forced by vbseo team which refuses to add hooks in their code which would allow to plugin vBET functionality. So please give your complains to vbseo team which by their mod architecture and by their politics (we publically asked them for hooks ant it was refused) - in other words you can thanks vbseo team for that. We realize what code changes means - why are you even write it to us? We already told you - you have full right to refuse integration and to accept potential issues with links and redirects and that you will not have translated URLs. vBET is great software which uses all possibilities to make our users live easier - proof: if you will use vBulletin Friendly URLs instead of vbseo you will have to do NO CHANGES AT ALL. It is because vBulletin made it in great way which allows to expand - vbseo made it in crappy way and they shake their asses in fear every time someone ask them to allow for expansions. Address your complains to vbseo team. This discussion has no sense and takes us nowhere. We are here to help you with your issues - please go back to issue. If issue do not exists anymore we will set it solved.
2.) I do not know your akamai CDN services or where do you have re-writes. I can guess that you have it in .htaccess or in vbseo - what would mean that you had to do it first in third party to meet requirements of other plugins... Please stop it - it doesn't have any sense. Do you have an issue or not? Configuration of your environment is normal administration task. You made it before and you will made it again. And each time you made it to meet some requirements - not for pleasure, so why you act now like you do something extraordinary? It is normal thing to configure your environment. More dependencies more effort and so on... Nice chit chat giving us nothing, so I propose to close it

We suggest to use test forum or to disable vBET for waiting time if you have some critical issues which cannot wait. About all other issues - please open new thread per new issue.

Ok - we have confirmation that the issue is solved. If the issue will go back then please write here we will gladly help you

No idea where your from man, but my modifications to htaccess isnt modifying the code of a plugin

I fixed the links issue myself :P there was no help here

[vBET]

There was help here form the very beginning - you wasn't wait an hour for our first reply I understand that you solved it without our hits, but still there was help from the very beginning

About vbseo code modifications - as you already know you can thanks for those to vbseo team which officially refuses to make their code open for extensions. vBulletin Friendly URL is made in more better way and allows for that - that is why using vBulletin Friendly URL you will have translated URLs without any code modifications. That is simple - poor vbseo solutions means poor integration. Great vBulletin solutions means great integration. vBulletin have official supported and described architecture how to create mods which opens their own hooks (extension points). And many mods really do it. vbseo team refuse to do it in purpose - please send your complains to vbseo team - we already know your opinion and you already know the cause of why you are such frustrated with integration - because vbseo team refused to make their mod extensible No matter how many times you will repeat that you would like other solution - it is not up to us and we will change nothing here. Complain to vbseo to make their mod open for extensions. We believe that it also have no sense - their politic here is very strict: afraid everything and change nothing for external

Anyway - we are glad your issue is solved