Dreadknux

Now I understand that changes have to be made to the core codebase whenever a new version of IPB is written. But in the last couple of updates (3.0.3 and now 3.0.4) I have had skins that I have developed during the 3.0.1 era break completely on me, because of deprecated skin code and a complete disregard of the skin's CSS on browsers (possibly as a result of deprecated skin code). Now, as I have worked very hard on my unique themes and they are vastly different from the IPB default skin, simply implementing the Skin Differences published is easier said than done, nor should I expect to constantly update my skins in this manner.

I was led to believe that when 3.0.0 was released, that custom skins could be created without fear of them breaking in future releases. This has turned out to be a false belief. Skins made the second a brand new version is released should be supported 100% until the very end of that version's life cycle. If nothing else, I would expect the money I paid for this software (and services) to reflect this, considering I have no time in my life now to micro-manage my skins whenever an incremental update comes out.

IPS, figure out where you want to be with your skin design and stick to it, please! Stop changing your mind every twenty seconds and invalidating my custom skins. I would like some confirmation that this issue will not occur again in future updates, otherwise I might as well just not make skins for my forums again (what would be the point?).

Regards,
Svend Joscelyne.

Now I understand that changes have to be made to the core codebase whenever a new version of IPB is written. But in the last couple of updates (3.0.3 and now 3.0.4) I have had skins that I have developed during the 3.0.1 era break completely on me, because of deprecated skin code and a complete disregard of the skin's CSS on browsers (possibly as a result of deprecated skin code). Now, as I have worked very hard on my unique themes and they are vastly different from the IPB default skin, simply implementing the Skin Differences published is easier said than done, nor should I expect to constantly update my skins in this manner.

I was led to believe that when 3.0.0 was released, that custom skins could be created without fear of them breaking in future releases. This has turned out to be a false belief. Skins made the second a brand new version is released should be supported 100% until the very end of that version's life cycle. If nothing else, I would expect the money I paid for this software (and services) to reflect this, considering I have no time in my life now to micro-manage my skins whenever an incremental update comes out.

IPS, figure out where you want to be with your skin design and stick to it, please! Stop changing your mind every twenty seconds and invalidating my custom skins. I would like some confirmation that this issue will not occur again in future updates, otherwise I might as well just not make skins for my forums again (what would be the point?).

Regards,
Svend Joscelyne.

Now I understand that changes have to be made to the core codebase whenever a new version of IPB is written. But in the last couple of updates (3.0.3 and now 3.0.4) I have had skins that I have developed during the 3.0.1 era break completely on me, because of deprecated skin code and a complete disregard of the skin's CSS on browsers (possibly as a result of deprecated skin code). Now, as I have worked very hard on my unique themes and they are vastly different from the IPB default skin, simply implementing the Skin Differences published is easier said than done, nor should I expect to constantly update my skins in this manner.

I was led to believe that when 3.0.0 was released, that custom skins could be created without fear of them breaking in future releases. This has turned out to be a false belief. Skins made the second a brand new version is released should be supported 100% until the very end of that version's life cycle. If nothing else, I would expect the money I paid for this software (and services) to reflect this, considering I have no time in my life now to micro-manage my skins whenever an incremental update comes out.

IPS, figure out where you want to be with your skin design and stick to it, please! Stop changing your mind every twenty seconds and invalidating my custom skins. I would like some confirmation that this issue will not occur again in future updates, otherwise I might as well just not make skins for my forums again (what would be the point?).

Regards,
Svend Joscelyne.

Now I understand that changes have to be made to the core codebase whenever a new version of IPB is written. But in the last couple of updates (3.0.3 and now 3.0.4) I have had skins that I have developed during the 3.0.1 era break completely on me, because of deprecated skin code and a complete disregard of the skin's CSS on browsers (possibly as a result of deprecated skin code). Now, as I have worked very hard on my unique themes and they are vastly different from the IPB default skin, simply implementing the Skin Differences published is easier said than done, nor should I expect to constantly update my skins in this manner.

I was led to believe that when 3.0.0 was released, that custom skins could be created without fear of them breaking in future releases. This has turned out to be a false belief. Skins made the second a brand new version is released should be supported 100% until the very end of that version's life cycle. If nothing else, I would expect the money I paid for this software (and services) to reflect this, considering I have no time in my life now to micro-manage my skins whenever an incremental update comes out.

IPS, figure out where you want to be with your skin design and stick to it, please! Stop changing your mind every twenty seconds and invalidating my custom skins. I would like some confirmation that this issue will not occur again in future updates, otherwise I might as well just not make skins for my forums again (what would be the point?).

Regards,
Svend Joscelyne.