Sajjad Ali

@smerriman Please update plugin to v2.0.2 and that should fix the Select Post Types issue. You can disable pages and other post types.

Let us know if there is still any problem.

Hello @smerriman

Did you try the Debug Mode option on the Settings page? That option should remove the bialty_container div. Please try that and let us know if it solves the issue.

As for pages not being disabled, I can confirm this bug, and it should be fixed very soon.

Thanks for reporting the issue.

Regards

Hello @andybrooks

The issue is most likely with Nginx permalinks settings. Here are the things you can try.

1. Enable Better-Robots.txt Plugin, go to Settings > Permalinks > Save changes
2. If that doesn’t solve the issue, try configuring Permalinks for Nginx. This guide might help with that.

Also, try disabling your cache plugins or Cloudflare cache for testing. Please note that your website is broken on my end as well (in Firefox, Windows). It’s not loading some CSS stylesheet for the homepage. The best way to debug is on a staging website. Try disabling all plugins and enabling only Better-Robots.txt to see if that works.

Let us know if this helps.

Regards

@cooperator_jr Thank you for reaching out. The issue has been resolved in Mobilook v2.0.1.

Hi @rebecaqs

Can you test it with latest version 1.4.7 and let us know if you still have this issue?

Regards

@joschi777

1. You don’t need ID parameter in this shortcode.

2. [wpgsv_map lat=”{{mpg_lat}}” lng=”{{mpg_lng}}”] should be sufficient. Also, make sure the commas are correct. It should not be a punctuation mark “”. In my full shortcode example, the commas are not correct.

3. Make sure that the MPG plugin is actually adding the correct lat and lng values inside those parameters. One way to test is to output them after the shortcode like this.

[wpgsv_map lat=”{{mpg_lat}}” lng=”{{mpg_lng}}”]
{{mpg_lat}}
{{mpg_lng}}

If the map location is incorrect, check mpg_lat and mpg_lng values and test them on Google Maps. If both values are correct then try it directly with the shortcode. for example, [wpgsv_map lat=”40.758896″ lng=”-73.985130″] (new york times square) and then check if that outputs the correct map. If that is working then it means {{mpg_lat}} and {{mpg_lng}} are not adding the valid values for some reason inside the shortcode. But If there is still an issue. Let us know.

Hi @joschi777

In the latest WP Google Street View v1.1.0, You can create dynamic maps with this new shortcode. There is no need to create a Map post.

[wpgsv_map lat=”value” lng=”value”]

This is the full example of shortcode with additional optional parameters.

[wpgsv_map lat=“value” lng=“value” width=“90%” height=“500px” zoom=“10” type=“street”]

Let us know, if that solves your problem.

@paktas That feature is already included in the Image Name option. Is it not replacing hyphens/dashes on your website? I just tested it on my end and it’s replacing them fine. Check this screenshot. https://i.imgur.com/sKXaajb.png

Also, it should replace any underscore or extra whitespaces with a single space and capitalize starting letter of each word.

Can you send us a screenshot/screencast of what it’s showing on your end when “Image Name” option is selected inside Bialty Settings?

Make sure your image names are including normal hyphens “-” and not em dash “—”. Kinda special long hyphens.

• This reply was modified 2 years, 3 months ago by Sajjad Ali.

Hello @tpetts

Can you please tell me, which page builder you’re using?

Regards

@janh2 Thanks for the report. It will be fixed in next update.

Hi @narolles

Yes. It’s tested with PHP 8.1.3. Working fine. Let us know if you find any issues.

Make sure that WP_DEBUG constant is set to false (it’s false by default) in wp-config.php. As it can display deprecated warnings with some wp core files if Yoast SEO is activated as well as multiple third-party libraries like freemius etc.

• This reply was modified 2 years, 6 months ago by Sajjad Ali.

@zohaibhasan810 Thanks for the report.

It seems your server can’t find the required class, causing a fatal error.

Please go to plugin folder /wp-content/plugins/vidseo and modify this file video-seo-transcription-embedder.php.

Go to line #25. Replace this line.

require 'vendor/autoload.php';

with this one.

require plugin_dir_path(__FILE__) . 'vendor/autoload.php';

Let us know if that fixed the issue.

I will release a new update to fix this.

Regards

Hello @narolles

Thanks for the report. We will look into this issue and hopefully, it will be fixed in the next update.

@ecolasurdo Thank you for reporting this issue. An updated version has just been released.

Regards

@dunar21 I feel the same. I have been banging my head since yesterday but can’t get the updated post meta value in the save_post action. And like you said, that post meta value is not available in $_POST/$_REQUEST object. So I don’t know how to get it. This should’ve been so simple.

WordPress docs says save_post “Fires once a post has been saved.” In this case, I should be able to get all updated post meta inside my function.

• This reply was modified 3 years, 6 months ago by Sajjad Ali.