SyGy

hello and thanks for the reply and explanation. I ask a question, but in doing so the location widget will not count the actual ads for example in “Rome”, so also the location page will not have results if the customer does not enter the location field?
In order for the widget and the location page to work, one must select it from the database.
It would be much more complete that a location is also populated with the data of the ads entered with API, not as regards the search (which may also be fine the search radius) but to have the directory with all the data categorized based on the locations.
But if this thing that for me is an improvement, for you it is only a waste of time, it’s okay! I will leave the places to people.
Thanks again and good day! And thanks for the excellent and fast technical support you give here on the forum !!

Hello! Thanks for the reply! I had already entered that option. but I had not noticed the option to see the choice of locations. I remove the check mark and leave the location via API. A piece of information, but if customers enter an address for example in rome via API localization, but do not select rome in the localities, can the plugin insert the ad in the rome location? ie the plugin can understand that that address located via API must be part of that location? maybe with keywords, if there is Rome inside the address searched with the API and if there is a location “Rome” automatically inserts that shop into that location! It would be a really nice feature.
Hello!

Hello! Thanks for the reply! OK I think it is absolutely essential when you have many locations and you don’t want to use the drop-down menu.
Hope the new version comes out soon? is there any indiscretion on the release date ?? Thanks and good job!

Resolved! the incompatible plugin was “All In One SEO Pack“. Eliminated and now everything is ok!

Hi also I have this problem, it shows me <span class = “……> in the name of the page. I understood from your answer that it was an incompatible plugin, which one? There is not a function to delete in order not to have the title changed?
Hello

Hi, not if it can be useful to others, but I managed to make the menu sticky in the mobile version. line 21 must be modified in the script.all.js file, inserting 1 instead of 991. Once the modification has been made, you must add this css, to enlarge the menu button to 100%.

@media (max-width: 767px){
/* menu mobile sticky */
.navbar{
width:100%!important;
}
}

I hope it helps some users who want to make the mobile version sticky too.

Hi, in the absence of the developer response. I tried to analyze the problem and I found a jquery script that blocked the scrolling of the page with submenus. The script should help with the operation but obviously it creates problems.
I commented on the offending script, which is located inside the /js/script.all.js folder:

				// Fix sub-menus for touch devices.
                /*
				 if ( 'ontouchstart' in window ) {
					menu.find( '.menu-item-has-children > a, .page_item_has_children > a' ).on(
						'touchstart.islemag', function( e ) {
							var el = $( this ).parent( 'li' );

							if ( ! el.hasClass( 'focus' ) ) {
								e.preventDefault();
								el.toggleClass( 'focus' );
								el.siblings( '.focus' ).removeClass( 'focus' );
							}
						}
					);
                 }*/

Commented on this script my page started to scroll quickly also on the menu.
I also made a function that allows you to make submenus clickable by name, so there is no need to click the arrow. this is the function to insert after line 112.

                container.find( '.menu-item a' ).click(
					function( e ) {
						var _this = $( this );
						e.preventDefault();
						_this.next().next( '.children, .sub-menu' ).toggleClass( 'toggled-on' );
                        _this.next( '.dropdown-toggle' ).toggleClass( 'toggled-on' );
                        _this.next().attr( 'aria-expanded', _this.next().attr( 'aria-expanded' ) === 'false' ? 'true' : 'false' );
                        if ( _this.attr('href') == "#" ) {}
                        else{
                           window.location.href = this; 
                        }
					}
                );

I hope it can be someone’s help.

Hi, I confirm that the latest version template has a floating menu problem. When you create submenus the floating menu has fluency problems. In my case I use a menu with 9 elements, the first 6 have a submenu, then two links to pages, and finally another submenu. In the desktop version there is no problem. But if I switch to the mobile version and open the menu, the page freezes, or better if I scroll the page with my finger, it doesn’t move. I have to click twice and then move the page, otherwise I have to put my finger on elements 7-8 (without submenus) and then the page slide is ok. As if the submenu created a problem with the floating menu.
Another problem with the mobile menu is that even if in the settings the option “disable the sticky menu” is not selected the menu does not become sticky when I scroll down the page, I saw the html code and the css class is regularly inserted “islemag- sticky “but it doesn’t do what the class has to do.
Another problem that I solved by editing the source code is the “apostrophe” after the writing “Related Articles” under the article. I noticed there was a ‘at the end of the <h3> tag. I eliminated the apostrophe and solved the problem. The file is “template-parts / content-single.php”
Is there a new version in mind to solve these problems?
To see my menu problem go to https://www.pilloledolanda.it in mobile mode
Thanks and even if I have these little problems it is an excellent template !!!

sorry, I only saw now that a custom css class that I had customized didn’t show me widgets in the footer. sorry if I sent this ticket.

precise that the check mark inside the widget configuration “only displays inside the directory” is not selected.
Thanks

hello and thanks for the quick reply. the missing widgets are in the footer. does not display categories and locations. it seems that it does not show me the widgets inside the pages that are not of the plugin. as seen in your screenshot inside the “directory” it works.