• Strange Issue (wp bug?): New sub-menu-item is MIA under certain circumstances.
    The test result is indicative of 7 unique instances of the same menu
    Avada only has one Menu defined.

    Menu has:
    1) 7 first level entries which are spread across the top horizontal menu bar
    2) the 2nd, 3rd, and 5th first level menu items have sub-items
    3) added a 6th sub-item to the 2nd first level menu

    Test Results:
    4) WP dashboard preview shows this 6th sub-item regardless of which of the top 7 first level menu items are in focus (which
    is the expected operation)
    5) from any of the following browsers; Edge, IE11, Firefox, or Chrome (tested on 3 pcs in 3 different geographic locations)
    a) if either the 4th or 6th top level menu item is in focus, hovering over the down arrow of the 2nd top level menu
    item shows the 6th sub-menu-item that was added
    b) if the; 1st, 2nd, 3rd, 5th or 7th top level menu item is in focus, hovering over the down arrow of the 2nd top level menu
    item this added sub-item is MISSING
    6) there is also an issue where when the 6th top level menu item is in focus it switches position with the 7th item on the menu
    bar (as a test, I had switched these items around but then switched them back … almost as though the WP HTML generator is
    using historic data to generate the home page)

    Current Metrics:
    – WP 5.7.2 en_CA
    – Avada 7.4.1
    – Avada Child 1.0.0 ThemeFusion
    – Linux 3.10.0-962.3.2.lve1.5.38.el7.x86_64 x86_64 Apache
    – PHP 7.4.19
    – cURL 7.74.0
    – mysqli 10.2.39 MariaDB
    – mysqlnd 7.4.19

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter vycwebmaster

    (@vycwebmaster)

    New information:

    This morning, for ALL scenarios of Menu top-level item focus, the newly added sub-item is now available PLUS the 6 & 7 top-level items are no longer changing places

    Highly suggests to me that this is a Server Side Issue most likely CACHED HTML pages … Not sure which of; AVADA, WP, APACHE/Linux, or Other, are responsible for determining when to send out old CACHED HTML pages … the expectation would be that whatever process is responsible for sending an HTML page would do some kind of “dirty” check in order to determine if a new page must be regenerated … there is a lot of noise on CACHE handling but I don’t know enough about what goes on behind the scenes to determine if there is something I can do to force a complete CACHE REFRESH (I installed a plugin called wp-optimize which suggested it does clear CACHED PAGES but running their free functions didn’t solve the issue)… basically my expectation is that if I make a change it should be available NOW not several hours later

    Thread Starter vycwebmaster

    (@vycwebmaster)

    You would THINK that the service provider would/should know THIS … AFTER MUCH TO DO IT WAS INDEED A CACHE ISSUE … NOT WP, and NOT the PLUGIN … THIS was a CACHE that needs to be cleared with the CPANEL CACHE MANAGER … is this an OS CACHE … whatever … I have NOW found a working solution with the passster plugin

    WP has a page protect option … can’t seem to get that working consistently
    AVADA has a page password protect option … can’t seem to get this to work at all
    AVADA also has a RESTRICT direct access option … can’t get this to work either
    passster once I turned off the Cookie Option in settings now consistently asks for a password for the page I need to be protected.

    Case Closed
    Thanks for listening … hopefully this may keep others from going down this rabbit hole

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Strange issue after upgrading to latest WP release’ is closed to new replies.