Ashok Singh
Forum Replies Created
-
Hello,
We have released a new version with fix of your issue.
Please update your plugin and let me know if the issue has been solved.
Best Regards
WePlugins TeamHello,
Thank you for contacting us.
At the moment, your KML layer is working correctly and there are no issues with the current setup.
Regarding the upcoming Google API changes, we are aware of them and will make the necessary updates in the plugin before they take effect, so it should not cause any disruption on your site.
For now, no action is required from your side.
Please feel free to reach out if you have any questions.
Best Regards
WePlugins TeamHello,
Thank you for contacting us.We tested this setup on our local environment with the Delay All JavaScript option enabled in the Breeze Cache plugin, and the map loaded correctly without any issues.
In addition to the files you already excluded, please make sure to also exclude the following JavaScript files:
js/maps.min.jsjs/maps.jsjs/wpgmp_frontend.min.js
These files are essential for rendering the map properly, and delaying them can prevent the map from displaying.
If the issue still persists after excluding these files, please feel free to reach out to our technical support team at [email protected], and they will assist you further.
Best Regards
WePlugins TeamHi,
Thank you for the clarification.
We’ve identified the issue and confirmed that there is a conflict affecting Font Awesome 4 icons when the map is loaded, especially with the latest version of Elementor.
Our team is currently working on a fix, and it will be included in the upcoming plugin update.
We appreciate your patience and for bringing this to our attention—it really helps us improve the plugin.
If you notice anything else or have additional details to share, feel free to let us know.
Best regards,
WePlugins TeamHi Breda,
Thank you for the clarification.
Our team is currently working on a fix, and it will be included in the upcoming plugin update.
We appreciate your patience and for bringing this to our attention—it really helps us improve the plugin.
If you notice anything else or have additional details to share, feel free to let us know.
Best regards,
WePlugins TeamHi,
Thank you for reaching out and reporting this issue.
We have tried to reproduce the problem on our local setup, but so far we haven’t been able to replicate the behavior you described. To investigate this further, could you please share the URL of the page where the map is displayed and the Elementor icons (e.g., fa fa-home) are not rendering?
This will help us analyze the conflict more accurately and work towards a fix in an upcoming update.
Looking forward to your response.
Best regards,
WePlugins TeamHello,
Sorry for the inconvenience caused.We understand your concern regarding the map height and responsiveness. Our team will be happy to assist you in achieving the desired layout and integrating dynamic map height as per your requirements.
Please feel free to reach out to us at [email protected], and we’ll help you with the proper solution and guidance.
Best Regards
WePlugins TeamHello,
If you have any further questions or concerns, please feel free to reopen the ticket.
Best Regards
Hello,
Thank you for contacting us.
I’m not fully clear on your requirements yet. From your message, it seems you may want to display posts on a map.
There are three different ways to display Custom Post Type (CPT) markers on the map. Please refer to the following tutorials:
- Assign locations using the ACF plugin:
https://www.wpmapspro.com/docs/how-to-assign-location-using-acf-plugin - Show post locations using custom fields:
https://www.wpmapspro.com/docs/how-to-show-posts-location-using-custom-fields - Display posts using the location meta box:
https://www.wpmapspro.com/docs/how-to-display-a-single-location-post-dynamically-by-using-a-shortcode-parameter
These features will be available only in the Pro version.
(https://weplugins.com/membership/)
If these tutorials do not fully match your use case, please elaborate on your requirements in more detail. I’ll be happy to guide you further.
Best regards,
WePlugins TeamsHello,
Thank you for reaching out.
To help us investigate this issue further, could you please share your details and this message with [email protected]? Our developer will review the issue and assist you in fixing it.
Looking forward to your email.
Best regards,
WePlugins SupportHello,
If you created the locations using our plugin’s Location Tab, then it is safe to delete all related post meta entries.
Our plugin stores locations in its own MySQL table, so removing those meta entries will not affect the data.Thank you for your suggestion regarding excluding posts and products by default. I will share this feedback with our development team, and they will review it for future improvements.
Thank you
Best Regards,
WePlugins TeamHello,
Thank you for contacting us.
If you do not want to use any post or page to create locations, please disable it from the Settings page. There you will see all available custom post types. Once disabled, the location meta box will no longer appear on those posts, and no new meta entries will be stored.
If empty meta entries have already been created and you are not using those posts or pages to display locations on the map, they can be safely removed.
However, if you are using a custom post type to display location data on the map, please do not delete those entries, as they are required for proper functionality.If you would like assistance removing old entries, please contact us at [email protected], and our team will help you.
Thank you.
Best Regards
WePlugins TeamHello,
Thank you for contacting us.
To help identify the issue, please deactivate your other plugins one by one and check if the map starts working. Once you find the plugin that is causing the conflict, please let me know its name.
Also, kindly share the URL of your frontend map page so I can investigate further from my side.
For additional assistance, you can also reach us at [email protected].
Best Regards,
WePlugins TeamForum: Plugins
In reply to: [Advanced Posts Listing – Show Post List Easily] How to remove _blank?Hello,
Currently, this feature is not available in our plugin settings.
However, you can manually remove thetarget="_blank"attribute by editing the plugin file.Please follow these steps:
- Go to the following file:
wp-content/plugins/advanced-posts-listing/advanced-posts-listing.php - Open the file and search for target=”_blank”.
- Remove the
target="_blank"attribute from the code and save the file.
We’ll include an option to control this behavior in an upcoming version of the plugin. Once the update is released, you’ll be able to manage this directly from the settings.
Best regards,
WePlugins Team
Hello,
We have released our new version, and the Fontawesome issue has been resolved in this version.If you have any further questions or concerns, please feel free to reopen the ticket.
Best Regards