Hi @Rikard,

Thanks for the reply.

Fixed our issue by changing the above downloaded avia_google_maps_api.js file on these lines:

				if( data.tooltip_display ) 
				{
                                        infowindow.open( { anchor: marker, map, shouldFocus: false } );
					//infowindow.open(map,marker);
				}

In case you have not read this, see this issue on Google Maps: https://issuetracker.google.com/issues/190075886

Solves our problem for now.

Best,
Peter

Ditto that. Seems to happen on the WebPage type. It says:

ImageObject	
The property ImageObject is not recognized by Google for an object of type WebPage.

I saw the above link to the solution but will this be fixed in an upcoming release?

++Tx
Peter

Hello @ismael,

This code changes the subject line of the message that arrives to the administrator of the site, not the message that’s sent to the user. Hence, user still receives default “Thank you for your message!” and the above code overwrites the “E-Mail Subject” entered on Contact Form element in ALB.

Can you please double check?

++Tx,
Peter

Hello, the email subject of the message received by the user cannot be customized as it defaults to “Thank you for your Message!”.

Could this be included as a field for the Contact Form in ALB?

@Yigit made reference to this above as the “Message Sent label” but that does not seem to be a field on the Contact Form element.

++Tx
Peter

Thanks Rikard for your response. Got there. Cheers :)

Found “a” solution.

In the wordpress table “_usermeta” there exists a “meta_key” called “meta-box-order_page” for each “User_id”. I went to the “meta_value” of this key, and it seems this is where WordPress decides the order in which DIV boxes appear on the edit screen for each page (or post). When looking at the HTML code of the edit screen the Avia Layout Builder DIV “id” is “avia_builder” (check the HTML code).

In the meta key value for “meta-box-order_page” there is serialized data for the order in which div boxes are supposed to be sorted on the edit screen for the right column (“side”) and the main column (“normal”). See the BEFORE and AFTER values below of my user’s “meta-box-order_page” and you can see I changed the order of the “avia_builder” DIV id to the front for the “normal” column. This corresponded to the actual position that it was on the screen. This seemed to fix my problem.

“meta-box-order_page” value BEFORE:

a:3:{s:4:”side”;s:43:”submitdiv,pageparentdiv,layout,postimagediv”;s:6:”normal”;s:106:”wpseo_meta,revisionsdiv,avia_builder,postexcerpt,postcustom,commentstatusdiv,commentsdiv,slugdiv,authordiv”;s:8:”advanced”;s:0:””;}

“meta-box-order_page” value AFTER:

a:3:{s:4:”side”;s:43:”submitdiv,pageparentdiv,layout,postimagediv”;s:6:”normal”;s:106:”avia_builder,wpseo_meta,revisionsdiv,postexcerpt,postcustom,commentstatusdiv,commentsdiv,slugdiv,authordiv”;s:8:”advanced”;s:0:””;}

I simply put the “avia_builder” id at the beggining of the list.

One other important thing to note. Originally when I accidently placed the Avia Layout Builder on the side bar, I repositioned back to the main column at the bottom (below Yoast SEO). But then WordPress automatically placed it above Yoast SEO, and it seems it may not have updated the database value for “meta-box-order_page”.