webmasteral

So I was able to solve the problem by updating the following code in js\scripts.js

const buttonEntries = [ ... jQuery('button', form.$form).get() ].map(entry => [entry.name, entry.value]);
//const buttonEntries = [ ... jQuery('button', form.$form) ].map(entry => [entry.name, entry.value]);

---- and ----


/*Wpcf7cfForm.prototype.updateGroups = function() {
const form = this;
form.$groups = form.$form.find('[data-class="wpcf7cf_group"]');
form.$groups.height('auto');
form.conditions = window.wpcf7cf.get_nested_conditions(form);

};*/
Wpcf7cfForm.prototype.updateGroups = function() {
const form = this;
// Find the groups and make sure they are safely iterable
form.$groups = form.$form.find('[data-class="wpcf7cf_group"]');
// Set the height to 'auto' for each group
form.$groups.height('auto');
// Convert jQuery object to an array for iterable functionality
const groupsArray = form.$groups.toArray();
// Optionally, you can now loop over each group using forEach or another method
groupsArray.forEach(function(group) {
// Handle each group here if necessary
// Example: console.log(group);
});
// Now fetch conditions and assign them
form.conditions = window.wpcf7cf.get_nested_conditions(form);
};


I hope this information is helpful to you

I also got this error. I uninstalled and did a fresh install of the plugin.

I am now seeing this error in my browser

Uncaught TypeError: jQuery(...) is not iterable
    updateSimpleDom https://www.example.com/wp-content/plugins/cf7-conditional-fields/js/scripts.js?ver=2.5.6:111
    wpcf7cf_timeout https://www.example.com/wp-content/plugins/cf7-conditional-fields/js/scripts.js?ver=2.5.6:410

Also the animations are no longer working.

When digging through the error logs I finally found the following

PHP Fatal error: Uncaught Error: Class ‘Wbcr_Factory465_Requirements’ not found in /home/public_html/websites/wp-content/plugins/hide-login-page/hide-login-page.php:74
Stack trace: 0 /home/public_html/websites/wp-settings.php(473): include_once() 1 /home/public_html/websites/wp-config.php(81): require_once(‘/home/p11iqgg22…’) 2 /home/public_html/websites/wp-load.php(50): require_once(‘/home/…’) 3 /home/public_html/websites/wp-blog-header.php(13): require_once(‘/home/…’) 4 //home/public_html/websites/index.php(17): require(‘/home/…’) 5 {main}

thrown in /home/public_html/websites/wp-content/plugins/hide-login-page/hide-login-page.php on line 74

hope that helps

My thought was maybe because the plugin is not downloadable during this locked review process the update process isnt happening correctly.

There was no php errors sadly. No errors at all other then the custom url no longer working.

What happened is on the 27th the update was applied, after that links that normally pointed to (custom login url example: hello) pointed to wp-login.php like the login button went from /hello back to /wp-login.php

I tried to turn the plugin off and back on, change the url, hide the default url on/off the link for the login button did not change.

Rolling the plugin back to 1.1.7 caused the url to point again to the correct url.

I was not able to investigate the issue further as my clients customers were messaging about noting being able to login but if I had time I wish I could have checked the DB to see if the url value was being updated.

I should also mention this “bug” did not replicate itself on my other clients websites that also use this plugin but those updates were applied before the plugin was locked for review.

During the clients next maintenance window I was planning on DL the plugin from client A and uploading it to client B (the one that had the issue) and see if that solve the issue or if the issue re-appears.

• This reply was modified 1 year, 3 months ago by webmasteral.

After more tests it looks like everything is working correctly and I am going to mark this issue as closed and resolved.

Thank you again for your support in helping me set your plugin up correctly.

Waited 20min, tried the test again and that seems to have worked.

I still need to test and see if when a guest post is created and held for review a notification is created and sent.

I will preform more tests through the day and let you know if I have any future issues with notifications being created or sent.

When I set the skip timer down to 1 min (and wait 5min) between tests I am still getting a “skipped” This notification is very similar to another one sent less than 1 minutes ago for the same receiver

First test – 2023-10-18 11:00:55

Second test – 2023-10-18 11:05:19

Not sure why im getting the skipped message if longer then 1min has passed between notifications?

I have uncheck the box for Asyn Notifications and retesting the notification

Thank you for your continued support

WP-Cron is active and working but your notification plugin keeps giving me a

Error: The notification was set as “Scheduled” but the cron task is not found
(asynchronous)

When I followed the troubleshooting it said to install “Advanced Cron Manager” plugin. After installing that plugin I was able to confirm the WP-Cron is running just fine. I can also create a cron job inside that plugin but I need to type in the “hook” to be called to push the notification out.

What I would like to know is what hook can I use to create a cron inside “advance cron manager” so that your plugin no longer gives me the error
(“Scheduled” but the cron task is not found)

What cron task is your plugin looking for I guess is another way to ask the question?

I will need to wait for support to provide me with the correct “Hook” to use so that when a notification is created the correct cron exists and I no longer get the Error: The notification was set as “Scheduled” but the cron task is not found
(asynchronous)

• This reply was modified 1 year, 5 months ago by webmasteral.
• This reply was modified 1 year, 5 months ago by webmasteral.

after some future testing I was able to get a log to trigger. In the log I got the following error
Error: The notification was set as “Scheduled” but the cron task is not found
(asynchronous)

I am trying to add the cron task but I need the “Hook”

Can you provide me with the proper hook to use to trigger the cron to push out the notification.

I am using the advance cron manager per the trouble shooting documents

• This reply was modified 1 year, 5 months ago by webmasteral.
• This reply was modified 1 year, 5 months ago by webmasteral.

Thank you for your quick reply. It looks like the logs are empty so I can only assume that the event when creating the post didnt trigger.

I have checked my settings but will try to alter a few settings to see what works.

reset the plugin from V3 to V2 invisible and created new keys, this seemed to solve the issue as well.

I would be happy to upgrade your plugin to pro if that would allow me to accomplish the goal of restricting that part of core wp to the users while still allowing them to see and use the plugin they need.

Thank you for that info.

That does work in a pinch and does grant access for the user to the plugin they require but as a down side it also grants users access to the core WP “Plugins” page. This means the user now has access to deactivate and activate plugins. I would like to restrict the users access to these actions.

Is there any way of doing that?