ehren.

What a nice topic, happy to have helped along the way! 🙂

I've worked with @Michael R over the past few years on his custom themes and he's always been a great client to work with. Nice to see the extra effort he goes to in order to keep children and prying eyes away, very dedicated. Happy holidays Mike!

All ipsfocus themes have been discounted by 30% from today until November 30, 2018.

Iconmoon is only used for a couple of icons if I'm not mistaken. You could quite easily overwrite them with FontAwesome icons and remove the entire iconmoon file.

Hi there, I've just checked the purchase list and your username isn't listed. If you believe you've purchased this theme and renewed it in June, I'd suggest contacting the Marketplace moderators so they can look into this for you. If you are an active customer, you'll be able to download all of my updates for free 🙂

Thanks Marc, nice to hear! The Support team has always been great whenever I've needed help, I just figured I'd mention this minor speed bump since it seemed to be happening every now and then. I appreciate the reply! ?

Hello, I guess this is just a friendly feedback topic for the benefit of my own customers, which I'm submitting in an attempt to improve IPS Support Ticket responses. As a theme developer, customers quite often contact me with bug reports after IPS Support have told them the issue is caused by their 3rd party theme. After quickly checking the issue for myself and noticing the issue also happens with the Default IPS theme, I'm required to redirect the customer back to the IPS ticket system so the Support Staff can investigate further. This isn't a burden for myself, but I can understand the frustration from customers who are bounced between two support desks without a solution. If Support Staff could make a conscious effort to always check the Default theme before referring customers to 3rd party developers for a solution, I'm sure my customers would be greatly appreciative of the improved support times.

Is the css framework outdated? Yes, absolutely. As mentioned by Charles above, it was coded 4 years ago which is ancient in terms of web coding practices, especially front-end. Floats are used to align content (and some areas even fail to clear the floats), grid containers are structured with javascript, absolute positioning is used to position the user bar, dozens of classes assign various colours and font-sizes (in px) to text, and countless hard-coded hex values are scattered throughout the css. I've made sure my theme framework has kept up with modern trends (by using flexbox and grid) to fix many of these issues, so even though the default IPS framework is outdated, it's absolutely possible to modernize it a little. But I imagine a complete re-write of the HTML, css and theme system would be priority for v5. Is a 3rd party framework like Bootstrap the solution? No - and I think plenty of people have already expressed their views as to why. Bloated files, excess classes which are never used, non-prefixed classes (such as .ips), and the pressure to keep the software compatible with the latest Bootstrap version are just a handful of reasons. IPS needs to create a clean, versatile and modern style for version 5 if communities are going to survive in the future, and I don't think a Bootstrap copy/paste layout is going to achieve that.

I'm struggling to understand why that would be necessary - that's not true at all. Wrapping the content with .ipsBox or .ipsBox_alt would increase compatibility to all themes. As it currently stands, your app technically isn't compatible with the default IPS theme, since changing the background colour of your site (to #333 for example) will make your app unreadable. Surely you'd support a customer if they changed the background colour of their site - this is essentially the same situation, and certainly isn't a 3rd party theme issue. IPS failed to wrap content in 4.2, however they acknowledged it in the above topic (as did many other customers) and they fixed it in 4.3. Following their lead would be a smart idea for developers if they wish to maintain compatibility across themes. ?

Hello, Due to the absence of a bug tracker, I figured the feedback area was appropriate. I've been using the 4.x theme system ever since the 4.x beta's and have come across bugs that are seemingly fixed in one version, but broken a few updates later. After working with xenforo's theme system recently and failing to come across a single bug, I figured I'd report on issues with the IPS system so it can be brought inline with xenforo's success. My theme setup is a standard Parent/Child setup. I have one main parent theme which includes all of my standard code found throughout my themes. I then create child themes which inherit all of the customized code, and occasionally have their own modified globalTemplate file and "theme.css" file, which is a custom css file. All other files remain untouched, which means I simply need to edit the Parent theme and all child themes inherit the updated code automatically. Inherited template files: The first bug I've found is related to unmodified template files in a Child theme, as shown in the following screenshot. All template files are untouched except for globalTemplate, however the icons indicate that numerous template files have been modified instead of inherited. Opening these "modified" files shows a revert button. Once clicked, it reverts the Parent file back to the default IPS code, which certainly isn't the expected result. Clicking the revert button (which technically shouldn't even be shown since the file is inherited) should revert the template file in the Child theme, so it matches its Parent. Put simply, from my understanding, those red icons should be green. Upload new version: Another issue which is constantly reported by my customers is the "Upload new version" feature. I have recently tried this myself and also came across the same issues as my customers. From what I understand, this feature should replace the currently installed theme with the freshly installed version, while retaining theme settings and any code inside custom.css. All other files (including custom HTML or custom css files) should be replaced with the new code. Reports from my customers indicate that some template files aren't replaced, which results in a broken theme and means a fresh theme install is the only solution. This is quite frustrating for my customers since they must reapply all of their old settings (colours, logos, etc), and their members need to reselect the theme from the bottom Theme menu if they've modified their choice in the past. My experience of this issue happened a few moments ago, however it varies slightly to my customers. I was working on two forums: Site A has my Parent theme installed. Site B also has an identical version of the Parent theme, but it also contains a Child theme. The Child theme has a modified globalTemplate file and a modified theme.css file. For the sake of this example, lets assume I have removed the logo from globalTemplate, and I have added a red background to the site using theme.css I then edited one HTML file in the Parent theme on Site A. I wanted to transfer those changes to Site B, so I exported the theme from A and used the "Upload new version" feature on B. The Parent theme on B was replaced successfully (as expected). I then checked the Child theme. The globalTemplate file had correctly retained it's modifications (the logo was still removed - all good), however the theme.css file had been reverted back to the Parent theme.css file which means I had lost all of my previous (red background) customizations. Referring to my example from above: instead of having a Child theme with no logo and a red background, I now have a Child theme with no logo and a white background because my theme.css file was reverted after installing the updated Parent theme. That may sound a little confusing to read but if you break it down step by step, it should be easy enough to understand. There seems to be a few issues with Parent/Child relationships and these issues may all be related in one way or another. Designers Mode: The requirement of enabling Designers Mode to create new theme settings is something which is unfortunately no longer a friendly option for me. My demo board had well over 100 themes at one stage, which means that enabling and disabling DM could potentially take hours, especially when all official IPS addons are installed. This means that even though I'd love to create new theme settings for my customers, it's no longer ideal due to the extremely time consuming nature. Contrary with xenforo, I simply enable their DM with one line of code and a "New setting" button appears in the ACP. If I add a new setting to the Parent theme, every Child theme also inherits the new setting. No template rebuilding is necessary, no time consuming processes, just a very easy way to add new settings - as it should be. Removing the line turns off DM, and everything is back to normal. Export Child theme: One final thought is the lack of an "Export child theme" option. IPB 3.x had this feature which was extremely helpful when managing a large amount of themes. Xenforo has this in both 1.x and 2.x, yet it has been removed ever since the initial 4.0 release for some reason. This means that once a Child theme is exported from a site, it can never be used as a Child theme again since it essentially becomes a Parent theme. If any of the IPS developers have any questions, or if I've incorrectly reported something, please let me know. The IPS theme system has silently struggled with these issues for a while and these small fixes would be a good start in helping to push the theme system back on its feet.

You can download the final release from your client area. ?

.ipsBox_alt{ background-color: {hextorgb="area_background_reset" opacity="1"}; border: 1px solid #e0e0e0; box-shadow: 0px 1px 0px rgba(0,0,0,0.1); border-radius: 3px; padding: 15px; }

Hello, The 4.3 updates will be started once 4.3.0 Final is released. My themes have never supported beta versions, sorry about that! I'll aim to have the themes updated within the first week of 4.3.0 though