Quote:
Originally Posted by b6gm6n
thanks for the screens, no screens, no install
|
Like that makes a difference to me

Rudeness will get you no where ...
Quote:
Originally Posted by Biker_GA
This..
Additionally, is there a way to remove the hardcoded version number from the templates? Or make it so when you do update VB, it allows the changes to be merged rather than having the "You have X outdated templates" glaring at you whenever you log in to AdminCP. 
|
I have a query which should sort out all those template conflicts:
---snip---snip---
UPDATE `
DBNAME`.`template` SET `version` = '
4.0.0', `mergestatus` = 'none' WHERE `template`.`styleid` =
XX;
/---snip---snip---
change
DBNAME to the name of your database,
XX to the styleid number of the mobile style and
4.0.0 to whatever the version number currently is.
4.0.0 worked for me with PL1. I subsequently changed it to 4.0.1 to see what would happened - it didn't have an issue, so you could probably up the version number to 4.0.99 if you wanted to - someone wanna test?
You'll have to change the above query to take any database prefix into account.