I like this better because it seems more "XF native". I'm sure it's easier to upkeep than most DoH styles are if it's not dependent on other things.
I am migrating to something similar so that it can be the child of the parent XF style and update without issues.
I updated from a 2.3.4 DoH style to 2.3.6 when I updated to XF 2.3.6 and it was missing a template. They've still not fixed the issue.
Will be much easier when I have a solid, nice-looking (based on major CSS edits, but the core is the same), to merge child themes.
It's the last time I use a 3rd party style; I've had too many issues with 3rd party styles (not to single DoH out), having to wait on them to upgrade XF, that it's just not worth buying them anymore when I can invest in a solid style that'll merge with each core XF update without issue. I'm having one done based on XF's parent so that it will upgrade with XF with no issue.
I am migrating to something similar so that it can be the child of the parent XF style and update without issues.
I updated from a 2.3.4 DoH style to 2.3.6 when I updated to XF 2.3.6 and it was missing a template. They've still not fixed the issue.
Will be much easier when I have a solid, nice-looking (based on major CSS edits, but the core is the same), to merge child themes.
It's the last time I use a 3rd party style; I've had too many issues with 3rd party styles (not to single DoH out), having to wait on them to upgrade XF, that it's just not worth buying them anymore when I can invest in a solid style that'll merge with each core XF update without issue. I'm having one done based on XF's parent so that it will upgrade with XF with no issue.