ThemeBurn Support › Forums › OpenCart Themes › Pavilion OpenCart Theme › BurnEngine (Pavilion 2) BETA bugs
This topic has been marked as not resolved.
@adimpacto, which cache system are you referring to ? |
|
February 3, 2016 at 5:44 pm #44670
|
|
Hi BurnEngine, Can you already confirm my issue: font rendering problem. Br, Ultimatia |
|
February 3, 2016 at 8:26 pm #44671
|
|
@ultimatia – we confirm the font rendering issue. According to our investigations, it appears randomly on Chrome 48 only. We didn’t observe it on other browsers or lower versions of Chrome. It seems to be a chromium engine bug and we weren’t able to find a workaround. It also seems that this issue does not arise on Chrome 49 dev channel. For now the only solution is to wait for 49, which is due to be released on 29 Feb 2016. Regards, |
|
February 3, 2016 at 9:00 pm #44672
|
|
Hi ThemeBurn, Thank you for clarification! I thougt I spotted the bug also in IE but did some test and can`t find the problems anymore. So I guess you are right. Any idea why it is only with your theme (BurnEngine) in Chrome 48? I didn`t have seen the font rendering issue on other websites (even not on the regular Pavilion theme). Best regards, Ultimatia |
|
February 3, 2016 at 11:47 pm #44675
|
|
@ TB Support i mean the theme cache system, inside the template options, the Content cache is incompatible with my module, because have his own cache system. The module is advanced menu filter, and works all but i have to disable the BURN Content cache. Is there a way to only disable for this module? |
|
February 4, 2016 at 2:27 am #44682
|
|
You will need to register in order to post topics and read replies in the ThemeBurn.com support forums!
|
|
February 4, 2016 at 8:57 am #44684
|
|
@ultimatia – it’s true that this issue does not appear on Pavilion. We didn’t have time to investigate other themes though. The difficulty is in the random appearance – it happens sometimes (most of the time it’s ok) and is unpredictable, so we cannot isolate it easily with method of exclusion. We’re sure there are other cases on the market, because it’s not an scripting error that is caused explicitly by our coding. There are several related issues listed in the chrome bug tracker. As this problem appears on a particular version of Chrome only, it’s most likely connected with an edge case combination of using custom fonts and some advanced styling techniques, which are not properly handled by chromium v48 font rendering engine. The best part is that Chrome is updated automatically everywhere, so there is no chance that some users will stay with v48 for long after v49 comes out in three weeks. That’s why we decided to not spare additional time on the problem and focus on bug fixing and feature additions. Should it appear on another browser or another version of Chrome, we will make it top priority issue. Regards, |
|
February 4, 2016 at 10:13 am #44685
|
|
BETA6 released. All of the reported issues have been fixed and the shared folder has been updated. Just re-upload and overwrite the existing files. For Beta6 you need to uninstall and install again the Stories module (from OpenCart modules) and the SEO Pack module (within the BurnEngine panel). You should also enter the `BurnEngine panel -> Theme Settings -> Colors` and just hit ‘Save colors’. If you continue to receive errors or notifications (you shouldn’t normally), you may need to re-install the BurnEngine module (just uninstall it and install it again from the OpenCart modules menu). Regards, |
|
February 4, 2016 at 11:51 am #44688
|
|
Thanks again for clarification! Agreed for sparing no additional time on this not so important problem. Updated to BETA6 and no issues so far. Oow 1 issue btw: still this errors when I enable the SEO Pack module
|
|
February 4, 2016 at 12:52 pm #44691
|
|
@ultimatia – we will investigate this one. Also, please, turn off the ‘minify HTML’ option as there is a bug, which is due to be resolved in the next release. |
|
February 4, 2016 at 1:48 pm #44693
|
|
@TB Support No, the module doesnt appear under System->Cache->Content blocks, do you have some documentation of how to make compatible module to appear there? or some other trick?
|
|
February 5, 2016 at 1:03 am #44703
|
|
After instaling BurnEngine, at first new theme wasn’t applied though I double checked if BurnEngine was swiched on in site settings. Then, after swiching to default layout and to burnengine again there is this fatal error on my site: Fatal error: ‘Color inheritance issue |
|
February 5, 2016 at 5:53 pm #44711
|
|
Ok, everythings fine. I didn’t save the theme colors as it was suggested. After saving them everything’s OK. But apparently BurnEngine needs to be double saved to be implemented as a theme. After initial instalation site showed stock Opencart theme though BurnEngine was chosen as default. |
|
February 5, 2016 at 6:23 pm #44712
|
|
Updated to Beta6. Few remarks: |
|
February 5, 2016 at 7:58 pm #44715
|
|
Live Preview doesn’t work in beta6, or is it just me? |
|
February 6, 2016 at 3:24 pm #44722
|
- The topic ‘BurnEngine (Pavilion 2) BETA bugs’ is closed to new replies.