Tareq Hasan

I don’t see any undefined* things in your linked page and it’s not a plugin feature. Can you record a video explaining your situation?

Right now, by default, the comments are off for the docs post type. The commenting option will come in a future version.

The plugin doesn’t automatically generate the introduction page, you create it. No, the linking can not be done because of how this WordPress and hierarchical post type works.

Thanks a lot Justin, means a lot ??

Shortcodes are for frontend only. But you could try like this:

if ( ! class_exists( 'WeDocs_Shortcode_Handler') ) {
    require_once WP_CONTENT_DIR . '/plugins/wedocs/includes/class-shortcode.php';
}

WeDocs_Shortcode_Handler::wedocs();

You won’t have any CSS styles though, you’ve to manage your own.

Just released version 1.5 with comment support. You’ve to enable comment from weDocs settings page. Then you can add comments on a single doc. Also, if the comment is turned off on every single docs, you’ve to turn those on as well.

The translations are not in my approval area. Only editors for portuguese can approve those translations. Can also ping anyone of them for approval?

Thanks for the translation ??

Thanks a lot ??

Sure, will fix this. Thanks for the heads-up ??

Yes of course. It supports the GTAG ??

Please see the video and configure exactly: https://youtu.be/WozaMIwgRlo

As weDocs is a custom post type, I think Polylang should already be supported. Did you check enabling post type support from Polylang?

I’m using Yoast SEO’s sitemap feature and I can see the sitemap is generating as usual. What sitemap plugin are you using? As it’s a custom post type, any sitemap plugin should be able to put the links into the sitemap.

Thanks a lot @bdombro for your kind words ??

You’re missing the whole point of this ticket, it’s getting the wrong folder. Look at the fopen() value of the topic, the ABSPATH and path to the .htaccess file is merged into one and that’s why getting the duplicated path.

Don’t get me wrong, I’m just trying to help to get this error away.

I’ve debug-bar installed, seeing the warning there.

Running plugin version: 1.8.18

I can see the @fopen() in the 98 line as well. I running valet locally, also can see the same error in production site.

It tries to create storage folder on admin_init and fails. The Nginx checking isn’t there.

Screenshot