Inconsistent theme HTML

[ehren.]

The /terms and /privacy pages also fail to use the ipsBox class so the text cannot be read if a background image is used.

To the IPS staff: Is it possible to get an ETA of when these fixes might be applied? Customers continually report these problems to me to me but it's technically not an issue with my code

[Michael R]

Any update on this?

[Lindy]

It's in the works and we'll address it as soon as we can. 

[Square Wheels]

9 hours ago, Lindy said:

It's in the works and we'll address it as soon as we can. 

Thanks, it is a real (first world) issue.  Let's say you have 5 themes, and there is an IPS update.  After I reinstall all of the themes because the update process doesn't work, then how do I know who was using what theme?  It tends to make users frustrated that with an update they also get reset to a default theme.  With hundreds of users or maybe thousands, I am not going to track and reset their themes for them.  So what should have been a minor security update that would have no effect on them turns into "what happened, everything is different, I really don't like the new updates...".

[MiP1]

Can anybody please confirm it is fixed in 4.2.4 beta? Or I just fail to reproduce it at the moment? 

Sorry, nevermind. Still not working  

[Mark Round]

Why did this change even happen? It's caused so many problems for me !!!

[ehren.]

Another report from a customer: uploading profile pictures.

[Michael R]

Frustrating

[LiquidFractal]

Sorry if this was already mentioned, but here's another example - when clicking/tracking a PM's IP:

[LiquidFractal]

Bumping, because, well, it's important.

[Michael R]

Is there an ETA on this? I have CORE pages that look terrible with ANY theme.

[Hezeber]

I'm another of ehren's customers who would love to see a fix for this. It's the one flaw that keeps the otherwise beautiful templates from being perfect, and unfortunately it's a pretty big flaw.

[aia]

• /terms/
• /contact/
• /login/
• /register/
• /privacy/
• /lostpassword/
• /messenger/
• /messenger/compose/?to=<uID>
• /modcp/ip-tools/
• /modcp/approval-queue/ (first run / empty queue)
• /modcp/reports/<rID>/
• /profile/<uID>-<uName>/edit/
• /profile/<uID>-<uName>/photo/
• /profile/<uID>-<uName>/?do=coverPhotoUpload
• /profile/<uID>-<uName>/warnings/add/
• /profile/<uID>-<uName>/warnings/
• /profile/<uID>-<uName>/warnings/<warning-ID>/
• /topic/<tID>-<tName>/?csrfKey=<key>&do=modLog
• /topic/<tID>-<tName>/?do=splitComment&comment=<cID>
• /topic/<tID>-<tName>/?do=editComment&comment=<cID>
• /topic/<tID>-<tName>/?do=featureComment&comment=<cID>&csrfKey=<key>
• /index.php?app=core&module=system&controller=poll&do=voters&id=<pollID>&question=<qID>&option=<oID>
• Offline screen (showed to all groups except admins when "Forum Online" is set to false).

[aia]

*added some more examples in list above.

[Arthmoor]

Getting the same problem with downloads in the "Add New Version" menu.

Same kind of thing with the "Edit Details" menu in a download entry.

[LiquidFractal]

On 10/6/2017 at 1:38 AM, Mr 13 said:

/register/

+++.  The registration page is a DOG'S BREAKFAST where other themes are concerned.  Enough to make people not want to register on your site!!

[Michael R]

On 10/15/2017 at 3:48 AM, liquidfractal said:

+++.  The registration page is a DOG'S BREAKFAST where other themes are concerned.  Enough to make people not want to register on your site!!

I get this complaint all the time.

[LiquidFractal]

@TAMAN's Backstretch plugin is great, but it's added to the list of extensions which suffer from the inconsistent theme HTML.  Changing the background on the default Invision theme presents all the familiar problems as per the above screenshots.

Hoping this is resolved very soon...

[Steph40]

I just put these lines in my custom css to help with Backstretch on default theme:

/* body */
 #ipsLayout_body {
    background: rgba(217, 215, 215, 0.9);
    border: .155em solid #000;
    padding-bottom: 20px;
} 

Hope it helps someone.

[InvisionHQ]

I join the list of those who have encountered this type of problem. 

[MiP1]

Hi, is it now any better with the 4.2.6? 

(couldn't find the time to test it myself yet)

[ehren.]

5 hours ago, MiP1 said:

Hi, is it now any better with the 4.2.6? 

(couldn't find the time to test it myself yet)

Nothing seems to have changed with 4.2.6. Fingers crossed for 4.3.x..

[Michael R]

[DesignzShop]

@Lindy

If no one disputes what I'm saying below can you look into this?

The theme auto-update process does work as it's been written. I think there's a mis-understanding why it doesn't.  Let me explain..

 

• Let's say you create a custom setting and need to fire up Designers mode or do anything else that would require you to fire designers mode.
• You create or make changes to setting(s) desired.
• You turn designers mode off (possibly thinking you are done or one of many other reasons, like you need to see corrected changes etc..) 

From here let's say we load our theme into the auto-upgrader. This will work and all templates with changes will be marked and take effect correctly however....

Let's say instead of uploading our theme to the auto-upgrader we decide to make another change / add something / do something more etc... and fire designers mode again. Once we do this a second time what happens is designers mode no longer recognizes the changed template because it has not been changed from the last designers mode run. When this happens the template is not changed in auto-upgrading. The only templates recognized by the auto-upgrader are the changed files in the last run.

What it seems to come down to is you need to make all your changes in one shot. Now from here it also gets a little more interesting. 

When you make version changes while in Designers Mode, version changes has to be in concert with template changes. So you would change the version number and make theme changes all in one shot for it to run and update correctly using the auto-upgrader.

So, If someone misses just one upgrade or a dev just once misses their "One shot" deal, the end user would again be forced to re-install their theme fresh. So there's our issue. No matter what at some point everyone will need to install their theme fresh at some point. 

On a positive note, the end user gets to be current. 

The only answer seems to have the theme up-grader scan for file changes at anytime instead of just last DM use.

Now I may be wrong on this above. But this is how it appears to work for me. If I'm wrong, please share

------------------

I also do understand the other issues being mentioned here. This post was just to address changes when upgrading.

Kind Regards

[kar3n2]

I think we have to do all of this to get some stuff back how it was.  Cant be right having us do all this. Its not easy when you're not quite so savvy. Better learn fast then hadn't I?