derekwcodes

Yep, their API is dead – they lie on their site and have the nerve to have a PROMOTION going on

Limited Time Offer

$49.95 value

Get Multiple Accounts Addon Plugin for Free with the order of Premium API for WordPress or Multiple Users Addon

Adding these dudes to my shit list I will follow them and any plugin they make to not be trusted. I will also look for Trustpilot etc… and go ham. Online Criminals at this point. Even if they fix this shit I will never remove this review.

There need to be a way to report dead plugins and trash companies on here so they can be removed from the repository. They are steal money from people www.remarpro.com. REMOVE THEM!

• This reply was modified 1 year, 9 months ago by derekwcodes.

Yeah used to have a good service – key word used to.

I have to contact my card company and dispute now. I bought the Premium API and it doesn’t trigger the function to work in backend so I sent them 50 bucks for nothing. If I upgrade for a year service I should get a year service.

Yeah on mobile end it is just blank. I lost several high priced sales when I updated to 2.0 and above. It is a nice black button feature as I watch customers goto checkout no Paypal button nor black credit card button showed. So I rolled back to 1.6.21

?? this killed me for this month. But anyways at least rollback didn’t damage anything hopefully abandon cart kicks in and get them back to buying.

Just wanted to update you guys on the issues mobile and sometimes desktop view the buttons are not available.

Ok nice yeah it was a browser caching problem now it’s working, thanks.

Ok let me reboot my server and cache the page.

aioseop-count-chars.js:100 Uncaught TypeError: Cannot read property ‘then’ of undefined
at aioseopAddGutenbergEditorListener (aioseop-count-chars.js:100)
at aioseopAddEventListeners (aioseop-count-chars.js:56)
at HTMLDocument.<anonymous> (aioseop-count-chars.js:35)
at i (load-scripts.php:2)
at Object.fireWith [as resolveWith] (load-scripts.php:2)
at Function.ready (load-scripts.php:2)
at HTMLDocument.J (load-scripts.php:2)

aioseop-admin-functions.js:88 Uncaught TypeError: Cannot read property ‘innerHTML’ of undefined
at aioseopGetClassicEditorContent (aioseop-admin-functions.js:88)
at aioseopUpdatePreviewSnippet (aioseop-preview-snippet.js:80)
at aioseop-preview-snippet.js:57

Stops my Composer Button from being used in new update.

• This reply was modified 4 years, 11 months ago by derekwcodes.

This might be helpful as well. If you installed the 7.0 and want to rollback to an older version. You can do so but remember the permalinks get all messed up.

– I uninstalled version 7.0 and installed 6.4.16 and I was still not able to log out until I went to my permalinks and clicked saved to get it to revamp the permalinks and then it worked again.

This might work for some and not others but its worth a try. And get prepared if you like Theme My Login and want what they have to offer 49 bucks is not to bad for a version 7.0. Only thing I don’t like is they said something about not letting you use pages to shortcode – I like the way it is so I can customize the page with a shortcode. I did not like this ON THE FLY crap with the login, lostpassword, register pages. I like it so I can put the shortcode in it and customize the pages as I see fit.

I had to re-upload version 3.3.4 as well my site stopping handling came up with this error.

This page isn’t working
MySite is currently unable to handle this request.
HTTP ERROR 500

Reload

I fixed it I disabled a plugin or two and manually uploaded the woocommerce new version. I also did a debug in the wp-config file to see what plugin was acting up. Once I got the woocemmerce uploaded and activated I turned the other 2 plugins back on and now its all good.

• This reply was modified 6 years, 7 months ago by derekwcodes.
• This reply was modified 6 years, 7 months ago by derekwcodes.

Yeah, on first publish the articles are not pushing to discord anymore. I have to check Process Old Posts, then update my article.

The new update is still not working for the Subcategories on the shop page. When subcategories are selected it is showing products below it also still.

I have a question though why did you guys place the options in teh customizer it was working great in woocommerce main control panel.

• This reply was modified 6 years, 9 months ago by derekwcodes.

Nvm, I see you guys are working on a new version of fixes. Thanks.

The drop down menus are showing up below visual composer boxes. Even on regular menus via wordpres the drop down are below editor?

This is all after updating to WordPress 4.8.1.

Ok yes it is because of the wordpress update. The z-index in the editor.css main menu styling is not high enough. Need a fix fast.

I found this but do not know how to override the core style css. After inspecting the elements:

element.style {
border-width: 1px;
z-index: 65536;
left: 600px;
top: 31px;
width: 175px;
display: none;
}

z-index needs to be pushed up to 99999 or 999999 !important;
This needs to be done in the wp-includes/css/editor.css?ver=4.8.1
The problem is messing with core files you need hook via function.php so this fix stay put on the next update if they do not apply this to it.

Any answers to resolve this now that I located the issue?

No reply? Well, this is what I came up with. Since there is no update or reply. This might help until they see that it needs to be updated.

https://stackoverflow.com/questions/32860218/the-called-constructor-method-for-wp-widget-is-deprecated-since-version-4-3-0

Ok, in this file in plugin: woocommerce-collapsing-categories/includes/class-wcc-widget.php

Change: parent::WP_Widget to parent::__construct

<?php
class WCC_widget extends WP_Widget {

parent::WP_Widget {

/* Widget settings. */
$widget_ops = array( ‘description’ => __(‘Create an expandable list of product categories and subcategories.’,’wa_wcc_txt’));

parent::__construct( false, __( ‘WC Categories’, ‘wa_wcc_txt’), $widget_ops );

}

• This reply was modified 7 years, 7 months ago by derekwcodes.
• This reply was modified 7 years, 7 months ago by derekwcodes.
• This reply was modified 7 years, 7 months ago by derekwcodes.

Yes, I am getting this same issue in debug mode. Is there a resolve or update for this plugin to correct this error?

Notice: The called constructor method for WP_Widget in WCC_widget is deprecated since version 4.3.0! Use
__construct() instead.

• This reply was modified 7 years, 7 months ago by derekwcodes.