Online casino forums,Ph11 casino login.REGISTER NOW GET FREE 888 PESOS REWARDS!

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 38 total)

Forum: Plugins
In reply to: [Ivory Search - WordPress Search Plugin] Error on new version

(@wmodes)

Same situation as everyone else, I’m just grateful I had this plugin installed on only one website, and not the dozen or so I’m responsible for.

Forum: Plugins
In reply to: [Contact Form 7] Images don’t upload

Thread Starter Wes Modes

(@wmodes)

3 years, 7 months ago

Further investigation shows that the image does get mailed, so the form is uploading the file properly. But something changed in the new version of how it internally handles uploaded files. Here’s the relevant PHP in functions.php that handles uploaded images within the function that constructs a WP CPT.

// IMAGE
// Retrieving and inserting uploaded image as featured image
// CF7 uploads the image and puts it in a temporary directory,
//      deleting it after the mail is sent
// Before it deletes it, we will move into our media library,
//      and attach it to our post
//
// get file upload info from form
$uploadedFiles = $submission->uploaded_files();
// if we have an uploaded image...
if( isset($posted_data['field_image']) ){
    // move image from temp folder to upload folder
    $imageUpload = wp_upload_bits($posted_data['field_image'], null,
        file_get_contents($uploadedFiles['field_image']));
    // PC::debug("imageUpload:", print_r($imageUpload, True));
    // echo ("imageUpload:", print_r($imageUpload, True));
    //
    require_once(ABSPATH . 'wp-admin/includes/admin.php');
    // construct array to register this image
    $filename = $imageUpload['file'];
    $attachment = array(
        'post_mime_type' => $imageUpload['type'],
        'post_parent' => $post_id,
        'post_title' => $posted_data['field_title'] . ' - ' .
                        $posted_data['field_contributor'],
        'post_content' => $posted_data['field_info'],
        'post_status' => 'inherit'
    );
    // attach image to this post
    $attachment_id = wp_insert_attachment( $attachment, $filename, $post_id );
    // PC::debug("attachment_id:", print_r($attachment_id, True));
    // echo ("attachment_id:", print_r($attachment_id, True));
    // if we succeeded...
    if (!is_wp_error($attachment_id)) {
        require_once(ABSPATH . 'wp-admin/includes/image.php');
        $attachment_data = wp_generate_attachment_metadata( $attachment_id, $filename );
        // PC::debug("attachment_data:", print_r($attachment_data, True));
        wp_update_attachment_metadata( $attachment_id,  $attachment_data );
        set_post_thumbnail( $post_id, $attachment_id );
        // add image id (attchment id) to ad_image field
        update_field( 'ad_image', $attachment_id, $post_id );
    }
}

This is called by:

add_action('wpcf7_before_send_mail', 'save_my_form_data_to_my_cpt', 10, 3);

This reply was modified 3 years, 7 months ago by Wes Modes.
This reply was modified 3 years, 7 months ago by Wes Modes.

Forum: Plugins
In reply to: [Contact Form 7] Version 5.4 breaking confirmations – Verified

Wes Modes

(@wmodes)

3 years, 9 months ago

Not only does the confirmation icon spin and spin… There also seems to be a debugging statement in the JavaScript that is triggered when the console is open.

This reply was modified 3 years, 9 months ago by Wes Modes.

Forum: Plugins
In reply to: [Ajaxify Comments - Ajax and Lazy Loading Comments] Multiple comment forms reloading page on comment submit

Thread Starter Wes Modes

(@wmodes)

4 years, 1 month ago

Jan,

I fixed it and I have a suggestion.

How I Fixed It

Since this page has multiple comment forms per page, the plugin requires a unique ID for the comment form (but not the comment form container). So I added a unique id for each comment form. Most WP themes set this by default to #commentform. I changed it to #commentform-1234, where 1234 is the ID of the post.

In the call to comment_form() inside comments.php for my theme, I added the following code:

<?php
	$comments_args = array(
			// Change the title of the reply section
			'title_reply' => __( 'Leave a Comment', 'textdomain' ),
			// Change the ID of the comment form from #commentform
			// to #commentform-1234, where 1234 is the ID of the post
			'id_form' => 'commentform-' . get_the_ID(),
	);
	comment_form( $comments_args ); // Render comments form.
?>

This generates HTML, something like:

<form action="https://unavoidabledisaster.com/wp-comments-post.php" method="post" id="commentform-2839" class="comment-form" novalidate="">
. . .
</form>

We can use the selector “.comment-form” to select the comment form from the plugin config, and the plugin will use the uqique ID to modify the post when you submit a comment.

My Suggestion

While the Post Container Selector setting is specific about needing a unique ID for multiple comments per page:

Selector that matches post containers to enable support for multiple comment forms per page; leave empty to disable multiple comment form per page support. Please note: Each post container needs to have the ID attribute defined.

The Comment Form setting does not have a similar warning. My suggestion is to add a similar warning to the Post Container setting.

If you like, I can submit that suggestion as a feature request issue.

Again, thanks for the help.

Wes

This reply was modified 4 years, 1 month ago by Wes Modes.

Forum: Plugins
In reply to: [Ajaxify Comments - Ajax and Lazy Loading Comments] Multiple comment forms reloading page on comment submit

Thread Starter Wes Modes

(@wmodes)

4 years, 1 month ago

And here is me checking to see if I can successfully find the comments within the post containers:

>> $(".thing-content.comments #comments #commentform")
s.fn.init(68)?[form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, form#commentform.comment-form, prevObject: S.fn.init(1)]

This reply was modified 4 years, 1 month ago by Wes Modes.

Forum: Plugins
In reply to: [Ajaxify Comments - Ajax and Lazy Loading Comments] Multiple comment forms reloading page on comment submit

Thread Starter Wes Modes

(@wmodes)

4 years, 1 month ago

Which of these settings are you suggesting I need to modify?

Post container selector – Specifically says it needs an id assigned for multiple comments on a post
Comment form selector – Defaults to #commentform, left at default
Comments container selector – Defaults to #comments, left at default

I added an id for my Post Container Selector (‘.thing-content.comments’), but it still reloaded the page. Do either of the other two require a unique id?

Here’s the console output when I load the page:

[WP Ajaxify Comments] Initializing version 1.7.1
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Found jQuery 3.5.1
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Found jQuery blockUI 2.7
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Found jQuery Idle Timer plugin
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Multiple comment form support enabled (selector: '.thing-content.comments')
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Initialization completed
jquery-migrate-3.3.0.min.js:2 JQMIGRATE: Migrate is installed, version 3.3.0
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Initializing version 1.7.1
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Found jQuery 3.5.1
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Found jQuery blockUI 2.7
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Found jQuery Idle Timer plugin
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Multiple comment form support enabled (selector: '.thing-content.comments')
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Initialization completed

And here is me double-checking that it can successfully find the Post Container:

>> $(".thing-content.comments")
0: div#post-2839.entry-content.thing-content.clickable.comments.
1: div#post-3002.entry-content.thing-content.clickable.comments.
2: div#post-3018.entry-content.thing-content.clickable.comments.
3: div#post-3120.entry-content.thing-content.clickable.comments.
4: div#post-2825.entry-content.thing-content.clickable.comments.
5: div#post-3028.entry-content.thing-content.clickable.comments.
6: div#post-3049.entry-content.thing-content.clickable.comments.
7: div#post-3078.entry-content.thing-content.clickable.comments.
8: div#post-3111.entry-content.thing-content.clickable.comments.
9: div#post-2998.entry-content.thing-content.clickable.comments.
10: div#post-2864.entry-content.thing-content.clickable.comments.
11: div#post-2880.entry-content.thing-content.clickable.comments.
12: div#post-3107.entry-content.thing-content.clickable.comments.
13: div#post-2872.entry-content.thing-content.clickable.comments.
14: div#post-2924.entry-content.thing-content.clickable.comments.
15: div#post-2823.entry-content.thing-content.clickable.comments.
16: div#post-2892.entry-content.thing-content.clickable.comments.
17: div#post-2878.entry-content.thing-content.clickable.comments.
18: div#post-3144.entry-content.thing-content.clickable.comments.
19: div#post-3124.entry-content.thing-content.clickable.comments.
20: div#post-2996.entry-content.thing-content.clickable.comments.
21: div#post-2900.entry-content.thing-content.clickable.comments.
22: div#post-3138.entry-content.thing-content.clickable.comments.
23: div#post-3122.entry-content.thing-content.clickable.comments.
24: div#post-2894.entry-content.thing-content.clickable.comments.
25: div#post-2896.entry-content.thing-content.clickable.comments.
26: div#post-2884.entry-content.thing-content.clickable.comments.
27: div#post-2902.entry-content.thing-content.clickable.comments.
28: div#post-2898.entry-content.thing-content.clickable.comments.
29: div#post-2876.entry-content.thing-content.clickable.comments.
30: div#post-3101.entry-content.thing-content.clickable.comments.
31: div#post-3006.entry-content.thing-content.clickable.comments.
32: div#post-3115.entry-content.thing-content.clickable.comments.
33: div#post-2870.entry-content.thing-content.clickable.comments.
34: div#post-3000.entry-content.thing-content.clickable.comments.
35: div#post-2994.entry-content.thing-content.clickable.comments.
36: div#post-3128.entry-content.thing-content.clickable.comments.
37: div#post-2886.entry-content.thing-content.clickable.comments.
38: div#post-3126.entry-content.thing-content.clickable.comments.
39: div#post-3109.entry-content.thing-content.clickable.comments.
40: div#post-3103.entry-content.thing-content.clickable.comments.
41: div#post-3011.entry-content.thing-content.clickable.comments.
42: div#post-2882.entry-content.thing-content.clickable.comments.
43: div#post-2888.entry-content.thing-content.clickable.comments.
44: div#post-3014.entry-content.thing-content.clickable.comments.
45: div#post-3095.entry-content.thing-content.clickable.comments.
46: div#post-2630.entry-content.thing-content.clickable.comments.
47: div#post-3009.entry-content.thing-content.clickable.comments.
48: div#post-3178.entry-content.thing-content.clickable.comments.
49: div#post-2874.entry-content.thing-content.clickable.comments.
50: div#post-2836.entry-content.thing-content.clickable.comments.
51: div#post-3180.entry-content.thing-content.clickable.comments.
52: div#post-2866.entry-content.thing-content.clickable.comments.
53: div#post-3087.entry-content.thing-content.clickable.comments.
54: div#post-3093.entry-content.thing-content.clickable.comments.
55: div#post-3099.entry-content.thing-content.clickable.comments.
56: div#post-3089.entry-content.thing-content.clickable.comments.
57: div#post-3097.entry-content.thing-content.clickable.comments.
58: div#post-3184.entry-content.thing-content.clickable.animated.comments.
59: div#post-3186.entry-content.thing-content.clickable.comments.
60: div#post-3118.entry-content.thing-content.clickable.comments.
61: div#post-3105.entry-content.thing-content.clickable.comments.
62: div#post-2868.entry-content.thing-content.clickable.comments.
63: div#post-3076.entry-content.thing-content.clickable.comments.
64: div#post-3080.entry-content.thing-content.clickable.comments.
65: div#post-3085.entry-content.thing-content.clickable.comments.
66: div#post-3024.entry-content.thing-content.clickable.comments.
67: div#post-3113.entry-content.thing-content.clickable.comments.
length: 68
prevObject: S.fn.init [document]
__proto__: Object(0)

When it reloads the page, no errors are reported:

[WP Ajaxify Comments] Initializing version 1.7.1
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Found jQuery 3.5.1
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Found jQuery blockUI 2.7
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Found jQuery Idle Timer plugin
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Multiple comment form support enabled (selector: '.thing-content.comments')
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Attach form...
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search comment form (selector: '#post-3028 #commentform')... Found: s.fn.init?[form#commentform.comment-form, prevObject: S.fn.init(1)]
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search comments container (selector: '#post-3028 #comments')... Found: s.fn.init?[div#comments.comments-area, prevObject: S.fn.init(1)]
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search respond container (selector: '#post-3028 #respond')... Found: s.fn.init?[div#respond.comment-respond, prevObject: S.fn.init(1)]
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search comment paging links (selector: '#post-3028 #comments [class^='nav-'] a')... Not found
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search comment links (selector: '#comments a[href*="/comment-page-"]')... Not found
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Initialization completed

This reply was modified 4 years, 1 month ago by Wes Modes.
This reply was modified 4 years, 1 month ago by Wes Modes.
This reply was modified 4 years, 1 month ago by Wes Modes.
This reply was modified 4 years, 1 month ago by Wes Modes.

Forum: Plugins
In reply to: [Ajaxify Comments - Ajax and Lazy Loading Comments] Multiple comment forms reloading page on comment submit

Thread Starter Wes Modes

(@wmodes)

4 years, 1 month ago

Thanks, Jan. That was what I was guessing from the console output. I’ll examine the errors and see if I can provide the plugin config with the right selectors.

I’ll get back to you to tell you if it worked.

Forum: Plugins
In reply to: [Ajaxify Comments - Ajax and Lazy Loading Comments] Multiple comment forms reloading page on comment submit

Thread Starter Wes Modes

(@wmodes)

4 years, 1 month ago

To reproduce the problem, by leaving a comment:

Only registered users can comment, so you will have to register first at https://unavoidabledisaster.com/register/. Takes only a minute
After that go to https://unavoidabledisaster.com/
Scroll down to any item that has a hover effect, for instance, the duck/rabbit or the image that says Deep Thoughts.
Click on it to bring up a dialog bubble.
At the bottom of the bubble, you will see a link to comments (“Read 2 Responses”, etc). Click that.
In the comments modal, try leaving a comment
Observe that the page reloads and goes to the individual item page, rather than using AJAX (or in addition to using AJAX).

After reload the console log says the following:

wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Initializing version 1.7.1
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Found jQuery 3.5.1
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Found jQuery blockUI 2.7
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Found jQuery Idle Timer plugin
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Multiple comment form support enabled (selector: 'article')
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Attach form...
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search comment form (selector: '#post-2825 #commentform')... Found: s.fn.init?[form#commentform.comment-form, prevObject: S.fn.init(1)]
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search comments container (selector: '#post-2825 #comments')... Found: s.fn.init?[div#comments.comments-area, prevObject: S.fn.init(1)]
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search respond container (selector: '#post-2825 #respond')... Found: s.fn.init?[div#respond.comment-respond, prevObject: S.fn.init(1)]
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search comment paging links (selector: '#post-2825 #comments [class^='nav-'] a')... Not found
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search comment links (selector: '#comments a[href*="/comment-page-"]')... Not found
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Attach form...
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search comment form (selector: '#div-comment-32 #commentform')... Not found
WPAC._Debug @ wp-ajaxify-comments.js?ver=1.7.1:87
WPAC._DebugSelector @ wp-ajaxify-comments.js?ver=1.7.1:95
WPAC.AttachForm @ wp-ajaxify-comments.js?ver=1.7.1:289
(anonymous) @ wp-ajaxify-comments.js?ver=1.7.1:513
each @ jquery-3.5.1.min.js:2
each @ jquery-3.5.1.min.js:2
WPAC.Init @ wp-ajaxify-comments.js?ver=1.7.1:507
(anonymous) @ wp-ajaxify-comments.js?ver=1.7.1:638
e @ jquery-3.5.1.min.js:2
t @ jquery-3.5.1.min.js:2
setTimeout (async)
(anonymous) @ jquery-3.5.1.min.js:2
c @ jquery-3.5.1.min.js:2
fireWith @ jquery-3.5.1.min.js:2
fire @ jquery-3.5.1.min.js:2
c @ jquery-3.5.1.min.js:2
fireWith @ jquery-3.5.1.min.js:2
ready @ jquery-3.5.1.min.js:2
B @ jquery-3.5.1.min.js:2
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search comments container (selector: '#div-comment-32 #comments')... Not found
WPAC._Debug @ wp-ajaxify-comments.js?ver=1.7.1:87
WPAC._DebugSelector @ wp-ajaxify-comments.js?ver=1.7.1:95
WPAC.AttachForm @ wp-ajaxify-comments.js?ver=1.7.1:290
(anonymous) @ wp-ajaxify-comments.js?ver=1.7.1:513
each @ jquery-3.5.1.min.js:2
each @ jquery-3.5.1.min.js:2
WPAC.Init @ wp-ajaxify-comments.js?ver=1.7.1:507
(anonymous) @ wp-ajaxify-comments.js?ver=1.7.1:638
e @ jquery-3.5.1.min.js:2
t @ jquery-3.5.1.min.js:2
setTimeout (async)
(anonymous) @ jquery-3.5.1.min.js:2
c @ jquery-3.5.1.min.js:2
fireWith @ jquery-3.5.1.min.js:2
fire @ jquery-3.5.1.min.js:2
c @ jquery-3.5.1.min.js:2
fireWith @ jquery-3.5.1.min.js:2
ready @ jquery-3.5.1.min.js:2
B @ jquery-3.5.1.min.js:2
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search respond container (selector: '#div-comment-32 #respond')... Not found
WPAC._Debug @ wp-ajaxify-comments.js?ver=1.7.1:87
WPAC._DebugSelector @ wp-ajaxify-comments.js?ver=1.7.1:95
WPAC.AttachForm @ wp-ajaxify-comments.js?ver=1.7.1:291
(anonymous) @ wp-ajaxify-comments.js?ver=1.7.1:513
each @ jquery-3.5.1.min.js:2
each @ jquery-3.5.1.min.js:2
WPAC.Init @ wp-ajaxify-comments.js?ver=1.7.1:507
(anonymous) @ wp-ajaxify-comments.js?ver=1.7.1:638
e @ jquery-3.5.1.min.js:2
t @ jquery-3.5.1.min.js:2
setTimeout (async)
(anonymous) @ jquery-3.5.1.min.js:2
c @ jquery-3.5.1.min.js:2
fireWith @ jquery-3.5.1.min.js:2
fire @ jquery-3.5.1.min.js:2
c @ jquery-3.5.1.min.js:2
fireWith @ jquery-3.5.1.min.js:2
ready @ jquery-3.5.1.min.js:2
B @ jquery-3.5.1.min.js:2
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search comment paging links (selector: '#div-comment-32 #comments [class^='nav-'] a')... Not found
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Search comment links (selector: '#comments a[href*="/comment-page-"]')... Not found
wp-ajaxify-comments.js?ver=1.7.1:87 [WP Ajaxify Comments] Initialization completed

Please note that once you are on the individual item page (https://unavoidabledisaster.com/thing/deep-stoned-thoughts/?WPACUnapproved=0&WPACUrl=https%3A%2F%2Funavoidabledisaster.com%2Fthing%2Fdeep-stoned-thoughts you can submit a comment WITHOUT reloading.

Looking at the console log results, I feel like it might be pretty obvious to you what I’m missing. But it is still a mystery to me.

This reply was modified 4 years, 1 month ago by Wes Modes.
This reply was modified 4 years, 1 month ago by Wes Modes.

Forum: Plugins
In reply to: [WP ULike - All-in-One Engagement Toolkit] Pass parameter for new count?

Thread Starter Wes Modes

(@wmodes)

4 years, 6 months ago

After a test, it looks like the count is associated with an arbitrary id. So yes, it appears that I can add an arbitrary number before or after the id and still have it work.

Now, if I can only figure out how to get the id of the outer post that my CPT is inserted into.

Forum: Plugins
In reply to: [WP Paint - WordPress Image Editor] only one instance of babel-polyfill is allowed

Thread Starter Wes Modes

(@wmodes)

4 years, 8 months ago

This worked. Thank you for your quick response!

Forum: Plugins
In reply to: [WP Paint - WordPress Image Editor] only one instance of babel-polyfill is allowed

Thread Starter Wes Modes

(@wmodes)

4 years, 8 months ago

It appears to be a conflict with the Conditional Blocks plugins. Is there any way to workaround this?

Forum: Plugins
In reply to: [Insert Pages] “Use a Custom Template” doesn’t show “Custom Template Filename” in builder

Thread Starter Wes Modes

(@wmodes)

4 years, 8 months ago

There are two anomalies I mention in the article that I want to check if they are intentional.

Insert Pages will allow you to search for your CPT (handy!), but you have to specify the path to the custom content template.

If you are using Elementor or Beaver Builder, you also get a new Insert Pages block. You will have to specify the slug of the CPT you want (no search this time), but if your template has a proper header and is in the templates directory, it will be offered as one of the custom template options.

Are these two reversed behaviors what you see on your system?

This reply was modified 4 years, 8 months ago by Wes Modes.

Forum: Plugins
In reply to: [Insert Pages] “Use a Custom Template” doesn’t show “Custom Template Filename” in builder

Thread Starter Wes Modes

(@wmodes)

4 years, 8 months ago

Paul, I took what I wrote above and turned it into a tutorial that may help your users. I’d be honored if you read it and offered any comments.

Using WordPress Insert Pages plugin with your Custom Post Types and Custom Templates

Forum: Plugins
In reply to: [Insert Pages] “Use a Custom Template” doesn’t show “Custom Template Filename” in builder

Thread Starter Wes Modes

(@wmodes)

4 years, 8 months ago

Okay, I’ve learned a few things that will help others using Insert Pages to insert Custom Post Types (CPTs) using custom templates.

1. You may have reason to create a custom page template for your CPT (e.g., single-mycpt.php). But you probably don’t want to use it with Insert Pages, unless you want to insert your nav, header, and footer with every inserted page.
2. Many themes divide the business of presenting a post or CPT to a content template (e.g., loop-tepmlates/content-mycpt.php), which is a good practice. These templates are handling the presentation stuff inside the loop. This is the template you probably want to use for Insert Pages.
3. However, if you use the content template to present your post or CPT, many WP functions only work within “The Loop” (<?php while ( have_posts() ) : the_post(); ?>) to know what post we are referring to. In many cases, there are alternatives that work outside of The Loop. If you don’t have an alternative, you can move your Loop out of the single template into your content template.
4. For your content template to show up in the Insert Pages config block in Elementor or Beaver Builder, you need to include a standard template comment block at the top. Here’s the Post Type Template used since WP 4.7.
5. If you use a child-theme, there is a possibility that your default template directory is set to the parent themes folder. In that case, if you put your templates in the child-theme’s folder they won’t be found by Insert Pages. That may change in the future, but I don’t have a workaround for that. (I shifted from a child theme to my own theme which used the excellent understraps theme as a jumping off point.)

Hope that helps your users. Thanks for your responsiveness.

Forum: Plugins
In reply to: [Insert Pages] Error loading block: Invalid parameter(s): attributes

Thread Starter Wes Modes

(@wmodes)

4 years, 8 months ago

Interestingly, with Elementor, it works just fine. Edit and then re-edit no problem.

Viewing 15 replies - 1 through 15 (of 38 total)

1 2 3 →