Data443 Risk Mitigation, Inc.
Forum Replies Created
-
@italwebcom please see the latest version to address this 🙂
The string “Unknown Data Subject Message” is not in the gdpr-framework.pot language file. We will include the string in a future release.
Forum: Plugins
In reply to: [Tracking Code Manager] Many New Features in v2.0.7 PREMIUMYou’re welcome 😉
Can i close the ticket?Thank you
Hello,
you can login to phpMyAdmin to delete these options inside the table called wp_optionsIf you’ve uninstalled TCM, you can safely delete any wp_options table entry where the entries start with ‘TCM_’. If the plugin cleaner can’t remove these entries for you, you will need to access the wp_options table using the database access tool for your site.
Forum: Plugins
In reply to: [The GDPR Framework By Data443] Woocommerce checkboxThank you! We try our best! If you haven’t already done so we would appreciate a positive review on the Reviews tab 😉 Thank you in advance!
Forum: Plugins
In reply to: [The GDPR Framework By Data443] Problem with not registered visitorsversion 2.0.1 has just been released to resolve this issue. We also added a custom message you can edit for these.
@zittercraft ,
Version 2.0.1 has just been released and the developer docs updated.Forum: Plugins
In reply to: [The GDPR Framework By Data443] Woocommerce checkboxHi @uaisg ,
fix to the timing of the initialization has just been released!Forum: Plugins
In reply to: [Inline Related Posts] Word before link “READ” in other languagesOur current translation files are in the language folder of the plugin base folder. You can look in that folder for an example of a translation file.
The best place for your custom translation files, to preserve the files through a plugin update are the
/wp-content/languages/plugins/folder. The naming of the translation file is important. For example a spanish translation file must be named ‘intelly-related-posts-es_ES.mo’Forum: Plugins
In reply to: [The GDPR Framework By Data443] Woocommerce checkboxThank you for letting us know about this.
We found the reason for this problem and will release an update soon.
Thank for the explanation. That helped me to understand the problem. We will need to update the developer docs. We will also fix the plugin to continue supporting this feature.
I don’t understand the purpose of the call to PrivacyToolsController(). It merely duplicates what the [gdpr_privacy_tools] short code already does. Which explains why you need to do all 3 remove_action calls.
If you will use the entire section of code below, there will be no duplicates.
global $gdpr; $controller = new Codelight\GDPR\Components\PrivacyToolsPage\PrivacyToolsPageController( $gdpr->DataSubjectAuthenticator , $gdpr->DataSubjectIdentificator , $gdpr->DataSubject , $gdpr->DataExporter , $gdpr->UserConsentModel ); remove_action('gdpr/frontend/privacy-tools-page/content', [$controller, 'renderConsentForm'], 10); remove_action('gdpr/frontend/privacy-tools-page/content', [$controller, 'renderExportForm'], 20); remove_action('gdpr/frontend/privacy-tools-page/content', [$controller, 'renderDeleteForm'], 30);You can contact me through our support portal: https://data443.atlassian.net/servicedesk/customer/portal/2/group/6/create/148
I need more information. You’re customizing the tools page but beyond that I need to be able to see the code and page results.
Can you provide code that would enable me to reproduce the problem you are seeing?