• Resolved dannyletham

    (@dannyletham)


    I am in a situation where, volunteering for an Older People’s Charity, I have been confronted with the writing on the wall for 3.40, and my suggestion has been accepted that the loss of some bespoke css features and the necessary reworking should be used as an opportunity to improve accessibility for the visually impaired.

    First, thanks for implementing changes to submenu colors etc. That is a big help. But now …

    I was dismayed to see that some of the options we might have considered per release 4.0.5 have been removed from the 4.1 rework of the Customizer, to the detriment of the product in general but certainly with a significant impact on our ability to scope improvements without the need (or indeed the option!) for extra coding. (Please bear in mind that all paid staff are non-expert, and dependency on this kindly but ageing Cobol Man is not desirable.)

    My immediate difficulty is this: the changes in functionality from 4.0 to 4.1 limit my ability to make firm plans with my non-expert staffers, and some reassurance that the product will not degrade further would be good! Better still would be some reinstatement.

    So, given the challenge as-is I have explored version 4.1.6 in some depth and with various extreme color choices with the joint aims of establishing both the nature of the tech and the parameters within which I can assist the staffers with their design.

    There follows a 12-point list. Of necessity in this topic header those points need to be made in brief, so the web page to which I have pointed is one that expands on them. In turn it links to some example screengrabs illustrating some of the issues.

    Plainly such a list requires some kind of prioritization. In order to tell the “story” I have listed them by type rather thn in order of importace. My prioritization would be:

    Most important, impacts on site design / production: 1,2,3,8,9 (but a quick answer to #8 please? as it requires no action and will help me with early stage planning.)
    Significant, detracts from product’s image: 4,5,10
    Of interest, needs doing: 7,11
    Least Importance, but be aware: 6,12

    OMISSIONS FROM SETTINGS
    1. Ability to define Sidebar Colors is compromised
    2. Setting for “Scroll to Top” option is missing.

    BUGS
    3. “GO” button is missing from search widget on sidebar.
    4. Sidebar and Footer widget titles do not respect Text Transform settings (but Colophon does!)
    5. There is a conflict between Sidebar and Footer titles’ behaviour regarding color.
    6. Header Border Color extends to full width regardless of “Full width header” checkbox setting.
    7. Menu layout bug related in some way to menu font size.

    QUERY RE COLOPHON WIDGETS
    8. Is colophon deprecated as reported in 4.0.5 or not as per 4.1.6?

    AESTHETICS
    9. Menu item separators have effectively gone missing.
    10. Line artifact 1, on header.
    11. Line artifact 2, on the footer.
    12 Ghosting artifact 3, on header.

    With thanks in anticipation,
    Danny L

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter dannyletham

    (@dannyletham)

    Okay, so today I see there is a 4.1.8, last updated 26 February, despite your having encouraged me to downoad the “latest” 4.1.6 on 11 March. I am confused!

    I’ll not update to 4.1.8 until I hear your views on my 4.1.6 findings, in case you need to look at the page as indicated under 4.1.6.

    @dannyletham You can rollback to the older version for now. If you want you can contact cyberchimps support directly if they have the bandwidth to help your website.

    @dannyletham We’re trying to create a balance between customizability, ease of use and speed. That’s why you’re seeing the changes in the customizer.

    1. Yes, we have as the box background color applies to both sidebar and main content but we will add it in upcoming versions.
    2. Scroll to Top is moved to the responsive pro plugin.
    3. Yes, the go button has been removed.
    8. No, the colophon widget is not deprecated and not going to deprecate in future versions as well.
    9. Yes, it has been removed as well.

    Regarding the remaining points, I would recommend you to contact CyberChimps support directly.

    Theme Author CyberChimps

    (@cyberchimps)

    @dannyletham

    Please raise the support on CyberChimps live site with website URL and screenshot.

    Thank you.

    Thread Starter dannyletham

    (@dannyletham)

    Can I do that for free theme and without a premium account? If so, how?

    Theme Author CyberChimps

    (@cyberchimps)

    @dannyletham

    Please raise the support on CyberChimps live site with website URL and screenshot. Our developer team will assist you over there.

    Thank you.

    Thread Starter dannyletham

    (@dannyletham)

    You said that already.

    My question is how do I do that without a paid account? Your support page assumes I have a login already and gives no option that I see do create one. My people are using the free version. Do they have to buy something?

    Theme Author CyberChimps

    (@cyberchimps)

    @dannyletham

    You don’t have to buy anything to get the support. Please raise a support request from contact page on CyberChimps live site.

    Thank you.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Visual appearance issues 4.1.6 and new customizer issues’ is closed to new replies.