Pro Burger Menu Module

v2.36.22026/11/13

• Performance: the rule that removes the z-index of .mm-page.mm-slideout with the menu in front was body:has(> .mm-menu--position-left-front, …), which the browser re-evaluates with each change in the children of (Style calculations were the biggest PageSpeed cost for io.genix). Now the JS puts rkr-menu-front in when creating a menu *-front and the rule is .rkr-menu-front .mm-page.mm-slideout. Tested on PS92 at 390 and 1440: z-index from the page car Same as before, and the menu is identical to the screenshot.

  v2.36.12026/11/12

  [sin destacar]

  • Fixed: The "Log in" / "Create an account" buttons in the My Account block no longer shared the width. 2.34.1. By limiting the base rule to .rkr-menu-scope .rkr-btn (flex: 1 1 auto) equaled in specificity to .rkr-account-cta .rkr-btn (flex: 1 1 140pxAnd won by coming later: in iO.GENIX, 184 + 208 px came out at 1440 (previously 196 + 196) and in a row at 390 (previously one below the other, 272 + 272). Now it is .rkr-menu-scope .rkr-account-cta .rkr-btn. Measured on PS92: 183 + 209 → 196 + 196 at 1440, as in the 2.31.1.

  v2.36.02026/11/12

  • The menu appears on the first gesture, not on loading. Mounting mmenu traverses the tree and forces page layout during loading; Lighthouse marked it as "Forced reflow" (in iO.GENIX, submenuMode and mmenu, 30-45 ms on the PageSpeed mobile). Now it loads when touching, hovering, or typing something that opens the menu (its buttons, the bar, "Other buttons that open the menu"), before the click. If the address brings #, It loads immediately. The current entry marker on the loading bar is still displayed. Measured on PS92 with CPU ×4: forced menu layout on loading 6 → 0 ms at 390 px and 50-103 → 0 ms at 1440 px.
  • submenuMode decide with matchMedia instead of reading window.innerWidth.
  • Accessibility: Buttons that open the menu without text or name (the theme or Elementor hamburger menu) receive aria-label "Open the menu"; in the menu bars, a.mm-btn without href it carries role="button" (and the one about returning, his aria-label) and a.mm-navbar__title no href role="none", ...also in the panels created afterward. Lighthouse treated them as untraceable links and unnamed buttons.

  v2.35.02026/11/11

  [sin destacar]

  • New hook actionRkrMenuItemVisibility, This allows other modules to hide menu items from a specific customer. It's triggered in the store (not the back office) for each item that the groups already make visible. ['item' => fila de rkr_menu_items, 'visible' => &$visible]; The listener puts $visible = false To remove it. It can only hide: what groups hide, no one reveals. The hidden entry remains marked in the tree. hidden, Just like the group ones, so the labels and the bar don't shift. RKR uses it for private products (rkrprivateproducts 1.1.0) with its subgroups of mail-order customers.
  • Without an upgrade: the menu doesn't register the hook; it's created by the module that listens for it upon registration. Without any listening module, everything looks as in the... 2.34.1.

  v2.34.12026/11/09

  • Fixed: Menu button styles (.rkr-btn, , .rkr-btn--primary, , .rkr-btn--ghost, , .rkr-btn--whatsapp) were applied to the entire store. Other modules of Rekire They use the same classes (RKR Influencer Promo) and their buttons appeared with the green menu reservation text and white text in the cart, the code welcome and the floating notice (seen in lacasadelassetas.com). Now they only affect the buttons that are inside the menu.

  v2.34.02026/11/09

  Four fixes that came out of changing the megamenu of a store with Elementor and categories only for professionals:

  • The labels and bar go with your entry, Not by their position. They were saved by their place in the tree, and a category that the client couldn't see (reserved for a group, deactivated, or empty) would be removed and shift all the categories behind it: with the "B2B only" category first, its "B2B" tag would appear in the second entry for all guests. Now, the entry that isn't visible stays in its place without being updated, and each selection carries its entry's ID, so the tag follows it even if the menu is reordered. Upon updating, the saved selections are automatically translated.
  • A CMS page can have entries under, like a link or a category: it acts as a gateway to a section ("Professionals" leads to their page and displays the registration and the catalog).
  • Centered bar: with the "Centered" alignment the bar appeared on the left (the generated CSS was invalid).
  • Other buttons that open the menu (New setting, in General): CSS selectors for theme buttons, such as the Elementor hamburger (.btn-toggle-menu), which open this menu instead of their own. Previously, JavaScript had to be added to the theme. Leaving it blank doesn't change anything.

  v2.33.02026/11/08

  Images also for products, pages, and links. The switch for each entry is renamed "Show images of what's hanging" and, in addition to the categories:

  • The products The listings hanging from the entrance display their cover (the one from that store), in the same grid as on the computer and the same list with thumbnails as on the mobile device. New format in the settings: Product image format (home_default (by default). WebP and AVIF are displayed if they exist.
  • The CMS pages, links, and titles They display it with its own icon at photo size. For best results, use a large PNG or SVG file.
  • In the grid, the photos in a row appear at the same height even if the names are different lengths. It uses the same switch as the... 2.31.0, So whoever updates sees the menu the same: it only changes an entry that already had it turned on and from which products or entries with their own icon hang.

  v2.32.12026/11/06

  On a dark background menu, the RKR Social Login buttons appeared with white text on a white background; only the icon was visible. Now the text is always dark.

  v2.32.02026/11/06

  RKR Social Login buttons in the "My Account" block, as in the RKR Cart Rewards side cart:

  • New switch in Lock my account. If RKR Social Login is installed and has any logins ready, its buttons appear under "Log in / Create an account" for those who haven't logged in; otherwise, the menu doesn't change.
  • When finished, the visitor returns to the page where they opened the menu.
  • The access key doesn't appear here: it stays on the login page.
  • It is turned on in new installations; the person updating has it turned off and sees the menu the same as before.

  v2.31.12026/11/03

  Two arrangements of the category images, seen when setting up the menu in a store with the Transformer theme:

  • The photo no longer extends beyond its memory card. When there are many columns: with 6, the card measured 135 px and the photo 140 and was mounted on top of the one next to it.
  • In the list with thumbnails, the photo and name are centered in the row even though the theme overlaps the mmenu layout; previously the photo stayed at the top and the name on the line below.

  v2.31.02026/11/03

  Images of the categories in the menu, with the photo on top and the name below, like the vertical menus of some themes:

  • Option per entry, "Show category images": Categories under this setting (from an automatic list or tree, and those added manually) display their images; in a subcategory tree, this applies at all levels. It's disabled by default: the user who updates will still see the menu.
  • Desktop grid with the columns selected in the entry (2 to 6). The menu widens accordingly; in "Two Columns" mode, the right column widens. The grid only illuminates if the open panel is large enough: otherwise, and on mobile, list with a thumbnail before the name.
  • Format and size In the settings, next to the brand logos: the store category formats with their dimensions, and if the chosen one is deleted, it falls into category_default or the first one there is.
  • WebP and AVIF when they exist: with If the file is there; the category without a photo appears only with its name. width/height of the format and loading="lazy", without any loading skips.
  • The long list (A-Z, columns) and grouped panel options do not apply to a panel with images. Exporting, importing, and copying the menu carry both settings.
  • New test: tests/imagenes.test.php.

  v2.30.12026/10/29

  Fixes that came out when using the 2.30.0 in a store with the menu migrated and on a server with ModSecurity:

  • "Activate" switch on each input. There was no way to hide an entry from the back office: unchecking all groups resulted in the message "To hide it from everyone, deactivate it," and there was nowhere to do so. Deactivated, it doesn't appear in the store or its sub-levels, and in the list, it's labeled "Deactivated." It only saves if the screen has the switch: one opened before the update doesn't turn it off.
  • The trash can also erases where the server cuts DELETE. The deletion was done using the HTTP DELETE method and some servers (ModSecurity with OWASP rules, limit_except (in nginx) they were responding with 403. Now it goes by POST; the route still accepts DELETE.
  • A new entry is left at the end. It was saved with its screen position + 1, and in a numbered menu 10, 20… (the one for a migration) the second one fell. Now the next number is given to the eldest of its sisters.
  • Sorting by dragging no longer creates a mess. Only the entries that changed position were recorded, with 1..N, mixed with the previous numbering of the others. Now all the sister entries are recorded.
  • A newly created entry can be dragged without reloading the page.

  v2.30.02026/10/28

  Each menu item can be limited to certain customer groups. In the entry form, under "Visible to customer groups": by default, all options are selected, making it visible to everyone, including groups created later. Unchecking one will cause your customers to no longer see it in the sidebar menu, header bar, or structured data, and its sub-levels will also disappear. Tags and entries selected for the bar will not be transferred to adjacent entries for those who cannot see them.

  Accordion-style sublevels, entry by entry. New "Expand sublevels accordion" switch: In the panel for that entry, entries with sublevels open below, in place, instead of moving to another panel. This applies to any level and to subcategory trees (for example, in "Gourmet," "Beverages," and "Food," their categories expand within the same panel). The general "Expand inline" setting remains the same and applies to the entire menu.

  Exporting, importing, and copying the menu to another store includes both settings; when importing to another installation, only the groups that exist there are retained.

  v2.29.62026/10/14

  The entire side menu is operated using the keyboard. Accessibility review of AhorraTinta (phase 7, at 375 px):

  • When it opens, the focus shifts to the menu. It is a modal dialogue (role=dialog, , aria-modal), but the focus remained on the button, and pressing Tab didn't take you to any category. Now it goes to the first item in the open panel.
  • The light bulb doesn't come out while it's open.The Tab key from the last menu returns you to the first, and Shift+Tab does the opposite. mmenu only leaves the page container inactive, and in many themes the header and footer are excluded.
  • When entering a submenu (sliding mode), focus shifts to the new panel instead of remaining on the previous one, which menu leaves inactive. Escape still closes and returns focus to the button.
  • Texts in Spanish For the screen reader: "Close the menu", "Open the submenu"..., which mmenu brought in English, and the dialog is called "Menu".
  • Each submenu button is announced with the name of its entry ("Consumables: Open submenu"). Previously, they all said the same thing, and in entries that are just buttons, that name covered the visible text.
  • The menu header logo link has a proper name when there is no text next to it.
  • The "Send an email" and "Call us" options in the contact block are no longer available. #B3B3B3 (2.1:1 on white) to about 6:1.

  v2.29.52026/10/14

  Three details noticed when setting up the menu in AhorraTinta (PrestaShop 9.2, a Hummingbird product):

  • The theme windows no longer appear behind the dark background. mmenu puts position:relative; z-index:1 to the page (.mm-slideout), and that encloses in a stacking context any Bootstrap window that lives inside (the cart notification, the zoom): the background, which hangs from With 1050, it remained above the window and its X. In the two positions offered by the module ("front"), the page does not move and the z-index is unnecessary: the module's CSS leaves it in car (bounded with :has(); without :has() Everything remains as it was). It had already been seen in maesalv9 with the 2.28.1, compensated on the subject.
  • Featured entry "text only". New "How they stand out" setting (RKR_MENU_BAR_HL_MODE: fill, the usual one, or text). In text The entrance has neither a bottom nor a veil inset 0 0 0 999px The hover effect—which previously left a gray box over a highlighted white background with red text—behaves like the others (underline, box, etc.) in its color and darkens the text on hover. An updated store remains in fill.
  • When newly installed, the bar only shows the button until the first time the configuration is saved (RKR_MENU_BAR_PENDING, only in a new installation and only while the connection is still in displayTopPreviously, it would render all top-level entries in the generated menu, and in a theme with a single-row header, this would increase to 273px. The button doesn't occupy its own row. Existing stores remain unaffected.

  v2.29.42026/10/12

  The settings screen can no longer fall apart completely. The PrestaShop Addons compatibility report gave "Attempts to access the module configuration page failed", in 8.1.2 for the 2.29.2 and in 9.0.0 for the 2.29.3. In the back office the screen opens fine, but when called with the context only partially active (without the Symfony core running, as a review tool does) it crashed:

  • The link to the menu editor was requesting the router to a Symfony container that didn't exist there. The backup for that case was already written, but it was hidden behind a catch (Exception) that does not capture the Mistake from PHP, so it wasn't used.
  • The form languages were requested from the controller without checking if they were available; now, if they are missing, they are calculated.
  • And if the form still can't be filled, the screen displays a warning and logs it in PrestaShop, instead of simply not opening. For the merchant, nothing changes: the screen remains the same.

  v2.29.32026/10/11

  On mobile, the accordion menu no longer gets stuck when scrolling. With submenus displayed in a line, if the finger started over an open submenu, the menu wouldn't move and the options below couldn't be reached (seen in a store using Hummingbird). mmenu leaves each panel overscroll-behavior: contain, Also in the accordion submenus, which do not have their own scroll bar, and that cut off the gesture before reaching the main panel.

  Furthermore, what the PrestaShop Addons validator flagged regarding the 2.29.2:

  • The module description is written in English in the code (in Spanish it still appears translated).
  • src/Service/IconGenerator.php It carries the verification of _PS_VERSION_.
  • In the diagnosis, the topic is read from the store instead of _THEME_NAME_, And there's one extra check that was always true.
  • In PrestaShop 8, the back office controller inherits from its base class by alias: the deprecated class no longer appears in a extends.
  • A numerical value from the generator template passes through interval, And PHP comments no longer quote HTML tags.

  v2.29.22026/10/09

  The module already includes its PrestaShop Addons product key (module_key), which Addons requires to accept the file. It doesn't change anything the visitor does or sees.

  v2.29.12026/10/07

  The menu is rebuilt with far fewer queries. On each page, the menu is rebuilt from the database, entry by entry: a menu product's entire record (about ten queries) was loaded just to retrieve its link, each CMS page was another query, each node in a subcategory tree loaded its category with all its languages, and the menu list was reordered six times. In a store with six products and ten CMS pages in the menu, the homepage goes from 105 to 15 consultations to the database.

  • The products and CMS menu pages are read at once, A query is performed by type, and the link is calculated based on that. If the store's product path uses price, tags, manufacturer, supplier, reference, or categories, the entire product is still loaded, as before.
  • Store menus are read once per request; they are read again if a menu or entry is created or deleted, or if a menu is imported.
  • The nodes in the subcategory tree no longer load the entire category. The menu the visitor sees it doesn't changeSame markup, same links, same hidden categories per group. There's nothing to reconfigure.

  v2.29.02026/10/05

  A true multi-store: each store, its own menu. Until now, the menu tree was the same for the entire installation: editing the menu in one store changed it in all of them. Now, everything that makes up each store's menu tree is unique.

  • The tree —its two menus, desktop and mobile, with all their entries—. The editor always opens the menu of the store chosen in the PrestaShop selector, and an entry from another store cannot be touched from here.
  • The adjustments. When you select a store, your data is saved for that store; when you select "All stores" or a group, it's saved for all stores within that area. The screen always displays which store or area you are currently in.
  • Custom CSS and HTML, one file per store.
  • The generator, who reads the store catalog; your copy to undo; ; import/export; ; bar tickets, and the diagnostics. The custom icon library remains common: these are files that any store can use. Updating does not change what any store displays. The existing menu is transferred to the default store, and each of the others receives an exact copy; their settings remain the same. From then on, each store is edited separately. New stores: If, when creating the new account, you copy the data from another account with this module enabled, you will inherit its menu, toolbar entries, and CSS and HTML. Otherwise, the first time you open the settings, the menu will be generated from its catalog.

  v2.28.12026/09/30

  The entries "Subcategories" and "Subcategory Tree" disappeared from the menu in any language other than the first one. The category was loading with the arguments switched places—the language was where the store was—so in language 3, you had to search in store 3: if it didn't exist, or didn't have that category, the entry wouldn't appear, without any warning. Just having a second language in a single store was enough to lose them; and where they did load, the label always appeared in language 1. Thanks to the customer who found it and pointed it out.

  v2.28.02026/09/27

  The menu can be generated from the catalog. New tab, Generate the menuIt reads the categories, brands, and content pages and suggests a complete menu. This is what used to have to be set up manually, entry by entry, in each store.

  • Seeing and applying are two steps. "View the proposal" He doesn't write anything.It shows the entire tree—which entry, of what type, and at what level—and only "Apply" writes it. A generated menu changes the navigation of a store that is selling, and that is checked beforehand.
  • Before writing, the menu that was there is saved., And there's a button to return it as is. If that copy can't be saved, nothing appliesIt is preferable to not generate at all than to generate with no way back.
  • The rules are chosen: how many entries at the first level, how far down it goes, the order of the families, the minimum number of products, and whether brands, content pages and contact information are added. What is generated sustains itself. Subcategories aren't written one by one: the family is created as "Subcategories," which are displayed on each visit. Brands are listed as "All Brands," and contact information as "Contact Page." A menu that simply lists items becomes outdated after the first category you create—and no one ever regenerates it—while one that delegates follows the catalog automatically. Two details that prevent a poorly generated menu:
  • Products are counted by entire branch. A family without its own products, whose subcategories do have them, is not empty: counting only its own products, it would be left out of the menu and would take half a branch with it.
  • The same catalog always offers the same menu. Two families tied for products are sorted alphabetically, so regenerating doesn't shuffle the store menu. And a fix unrelated to the generator but discovered along the way: with the store in development mode, the settings screen responded 500 As soon as there was an extra button saved and a language added LATER —the button has no label in that language and the PHP warning becomes an exception—. In production it wasn't visible; in development mode it crashed the entire screen.

  v2.22.12026/09/13

  • New You choose which entries appear in the horizontal bar, at any level, and whether each one expands or leads to its page.
  • New In the bar, a separate group on the right, a highlighted entry with its color and a short text per language.
  • Corrected The mobile submenu mode selected is respected, even when rotating the phone.
  • Improved The open branch is marked with a background, bold text, and a sidebar, to show where each submenu hangs from.

  v2.21.02026/09/12

  • Improved Your CSS, menu footer HTML, and icons are no longer lost when you update the module.
  • Improved If they cannot be moved due to permissions, the diagnostic tells you which folder to check.

  v2.20.12026/09/12

  • New Horizontal bar in the header that comes from the same menu tree, with thirty-two appearance settings.
  • New A bar entry with a submenu opens the side menu right by that branch.
  • Improved On narrow screens the bar retracts and only the menu button remains; you choose the width.
  • Improved Back-office fully translated into English.

  v2.19.42026/09/11

  • Corrected Importing the menu works with any type of input, and a failed attempt no longer leaves the menu empty.
  • Corrected Link-type entries display the submenus you attach to them in the store.
  • Corrected The menu is no longer located below the fixed theme header.
  • Improved The module returns to its place within the group of Rekire in the back-office menu.

  v2.18.4

  • Corrected The module's entry in the back-office menu is always visible, with its sections and permission for all profiles.
  • New Button to rebuild the back-office menu from the diagnostic panel.
  • Corrected Custom SVG icons no longer appear broken; saved icons are repaired upon update.

  v2.17.4

  • Improved All the settings in a single form with tabs and a single save button.
  • New Button to repair the back-office menu from the diagnostics, which explains what prevents it from being created.
  • Corrected The module entries in the back-office become visible again when updating from previous versions.
  • Corrected The settings tabs are no longer all displayed at once.

  v2.16.0

  • New New Settings section in the back-office menu, next to Menu Items and Custom Icons.

  v2.15.1

  • Improved The module is grouped with the rest of the modules of Rekire in the back-office menu.
  • Corrected It no longer gives an error when installed alongside another module of Rekire.

  v2.14.0

  • New The menu is inserted automatically on the page even if the theme does not call for it, without being duplicated.

  v2.13.2

  • Improved The menu also starts with themes that don't include all the usual hooks.
  • New Diagnostic panel that checks the installation and tells you what's missing if the menu doesn't appear.
  • Improved When you save the configuration, the module reconnects itself to the theme points that are missing.

  v2.12.0

  • New New entry type "All brands", with optional logos and configurable limit.
  • New Option to load separately any branch that exceeds a certain number of entries, regardless of its level.
  • Corrected The links in the blocks no longer appear more dimmed than the rest of the menu.

  v2.11.0

  • New Panel grouped in columns for desktop: each subcategory as a header and its children below, distributed individually in columns.

  v2.10.1

  • Improved Deferred loading is chosen by levels: the first ones go on the page and the deeper branches are requested when opening them.
  • Improved The menu header can be displayed on desktop, on mobile, on both, or on neither.
  • Corrected The animated button icon has been removed, which in some themes left the page blank.

  v2.9.0

  • New Close the menu by swiping your finger on touchscreens.
  • New Optional delayed menu loading, without losing structured data.

  v2.8.0

  • New The entry of the page where the visitor is located and its branch are marked.
  • New Optional preloading of menu pages on mouse hover.
  • Improved More accessible: the menu closes with Esc and the focus returns to the button.

  v2.7.1

  • New Set your own background color for the menu; if you don't set the text color, it will be calculated automatically.
  • New Option to hide the top bar with the title and close button.
  • Improved The module appears in the back office within the modules section of Rekire.

  v2.6.4

  • New "Inline display" submenu mode, recommended on mobile, and a separate mode for desktop and mobile.
  • New Structured menu data for search engines, with a depth limit.
  • New Google Gemini as a provider for generating icons with AI.
  • Corrected It is no longer necessary to install the module twice when uploading it.

  v2.5.2

  • New AI-powered icon generator based on the text of each entry, with review before application.
  • Improved The fixed header remains throughout the scrolling, without any flickering of the logo.
  • Corrected Column mode: correct width on mobile and is only deactivated if the columns do not fit.

  v2.4.2

  • New Menu header with logo, store name and custom colors.
  • New Five predefined designs: Rekire, Midnight, Soft, High contrast and Warm.
  • New Submenus in two columns, with the previous panel in view.
  • Improved Store texts translated into Spanish and English.

  v2.3.1

  • New Import and export the complete menu to a file.
  • Improved Extra buttons with four colors, rounding, and icons uploaded by you.
  • Corrected The list and menu blocks scroll together, and the hand-pasted SVG is already saved.

  v2.2.0

  • New Extra buttons above or below the menu, with their color and icon.
  • Improved Uninstalling no longer deletes your menu or settings, unless you choose a full cleanup.
  • New Ten new icons in the catalog.

  v2.1.0

  • Improved Compatible with PrestaShop 8 as well as PrestaShop 9.
  • New My account blocks, contact, social media, trust, and opinions.
  • New Search engine within the menu and click measurement in GA4 or Google Tag Manager.
  • Corrected The mobile menu no longer appears empty in some cases.

  v1.5.22026/07/23

  • Corrected The menu checks that the linked categories, products, and brands exist before displaying them.
  • Corrected Fixed possible errors when obtaining category names in each language.