How to clear retrieve log in plugin registration tool - plugins

I'm using plugin registration tool.
In the section: Debug -> setup tab -> Retrieve log -> 'select profile from CRM' popup, I need to clear all logs from 'select profile from CRM' popup.
How to do that?

This will be stored in CRM entity - Plugin Profiles. Delete the unwanted old records.
You can do Advanced Find for that entity or navigate to Settings - Extensions.

Related

Where else can I find alternate login URL aside from $CFG->alternateloginurl

I'm currently troubleshooting a login issue for a deployed Moodle. Login page uses an alternate page which I have managed to identify. The alternate page considers everything except successful login as invalid or expired login or password.
Since some correct login and password are also getting the same issue.I am trying to restore the Moodle instance to use its default login page but did not find any $CFG->alternateloginurl configuration set in moodle.php. Kindly please provide any pointers you can think of on where to look next to restore the login page.
PS: I've also searched within the active theme, and there has not been any code changes. Uses a variant of Moove
Thank you
Rest assured that its a common issue
https://docs.moodle.org/401/en/Managing_authentication#Alternate_login_URL
There is an entry in the database
SELECT *
FROM mdl_config
WHERE name = 'alternateloginurl'
Note the value, just in case, then blank it out
UPDATE mdl_config
SET value = ''
WHERE name = 'alternateloginurl'
Then purge the cache to update Moodle
php admin/cli/purge_caches.php
When you do manage to log in, check which other authentication methods are active via
Site administration > Plugins > Authentication > Manage authentication
https://docs.moodle.org/401/en/Managing_authentication
The default methods are manual and email self registration
Although self registration is disabled by default in the settings on the same page (registerauth)

We want to hide out of stock products from Magento2, which is already enabled with MSI

We want to hide out of stock products from one of my Magento2 project, which is already enabled with MSI.
But we are unable to do the same.. Any help will be appreciable..
In Admin Panel you can disable showing out of stock products:
Stores -> Configuration -> Catalog -> Inventory -> Stock Options -> Display Out of Stock Products -> No

Add new category and custom page into Site Administration menu

I'm trying to add a new feature into site administration menu of moodle as part of a project that I am working on. Right now our customer only needs to integrate OnePay gateway into moodle. But in the future, they may require integration of other payment gateways (like PayPal) as well. So I need to create a category just for website administrators to input different types of payment. A new category should be somewhere in the "Advanced Features" menu (something like in the following screenshots)
Where to add new category
Example for onepay integration
With "Settings" page is a page that site administrator to input all necessary payment information (including customer's card number, access code, etc.). Right now I'm testing with using two of my testing pages for domestic and international payments.
Here is my code in file /lang/en/admin.php:
$string['payment'] = 'Payment';
$string['onepay'] = 'OnePay';
$string['test_onepay_domestic'] = 'Test Domestic Payment using OnePay';
$string['test_onepay_international'] = 'Test International Payment using OnePay';
In admin_custom directory, I created a path like this /payment/onepay/test/ and add 2 my testing pages into it. In folder /payment/, I added a file named menu.php. Here is my code in it.
<?php
$ADMIN->add('advancedfeatures', new admin_category('payment', get_string('payment', 'admin')));
$ADMIN->add('payment', new admin_category('payment', get_string('onepay', 'admin')));
//$domestic = new admin_settingpage('onepay', new lang_string('test_onepay_domestic', 'admin'), new moodle_url("/admin_custom/payment/onepay/test/domestic/index.php"));
//$international = new admin_settingpage('onepay', new lang_string('test_onepay_international', 'admin'), new moodle_url("/admin_custom/payment/onepay/test/international/index.php"));
$domestic = new admin_externalpage('test_onepay_domestic', get_string('test_onepay_domestic'), "$CFG->wwwroot/admin_custom/payment/onepay/test/domestic/index.php");
$international = new admin_externalpage('test_onepay_international', get_string('test_onepay_international'), "$CFG->wwwroot/admin_custom/payment/onepay/test/international/index.php");
$ADMIN->add('onepay', $domestic);
$ADMIN->add('onepay', $international);
I have attempted to include file menu.php in both files
/admin/settings/top.php
/admin/settings/server.php
But none of these works. Can anyone please tell me what should I do to get this works? Thank you very much. I really appreciate that.
Moodle doesn't have any sort of plugin type called 'payment', so by creating a hierarchy starting '/payment', you're already at odds with the way that Moodle works (as shown by needing to edit core files in order to add language strings and menu items).
I would recommend that you start again by creating an admin tool or a local plugin. Both of these types can have their own language strings and can add entries to the site admin menu (have a look at the settings.php inside any of the standard admin tool plugins or, for local plugins, an additional option is to create a local_MYPLUGIN_extend_settings_navigation() function). If you want to support multiple payment options, then your plugin could define a new subplugin type for each of the payment options.

Get user list from Taleo Connect Client

We're using the Recruiting Taleo (14A) module and I was wanting to pull a list of external and internal users (login, email, internal/external, etc) from Taleo Connect Client (12A).
Does anyone know how to do this? Or where to pull the data from? Thanks
I believe the entity you are looking for is Candidate. Taleo Connect Client has a built in template for exporting candidates, which includes usernames and email addresses.
Open Taleo Connect Client and select File → New → New Export Wizard.
Click the Product dropdown and select your Taleo product version.
In the list of entities, select Candidate.
Under the Template section, select Create export from a template.
Click the Template dropdown and select Standard Candidate export (CSV-ENTITY).
Click Finish to create your new export.
Note: The candidate export template for Recruiting Taleo 14A appears to be based on Recruiting 10.0.1. This can be fixed either by creating an export without a template, or by changing productCode="PRO1001" to productCode="RC1401" in the source file.
You can customize your export's projections and filters to suit your needs. Alternatively, if you don't want to start from a template, you can create a new export instead.
Once your export is saved, you can run it by creating a new configuration.
Open File → New → New Configuration Wizard.
Select Based on an export specification.
Click the three dots ... next to File and select your export.
Click Next to move to the next page.
Select your Taleo Endpoint, then click Finish.
Save & run your configuration.

CakeDC Users Plugin: Disable/Override Username Validation

How to configure CakeDC's Users plugin to override/disable the username field?
I have reconfigured the plugin to use 'email' field as username for login - and it works great for login - but I no longer need the username field validation in the registration.
Any ideas? Thanks!
Using CakePHP 3.1 and CakeDC User plugin 3.1.3
You can override the Users table and configure your own validation rules, etc following this page in the documentation https://github.com/CakeDC/users/blob/3.1.x/Docs/Documentation/Extending-the-Plugin.md#extending-the-model-tableentity
Once you are done with the new Table, don't forget to pass the new table configuration to Users Plugin Configuration using the parameter
'Users.table' => 'MyUsers',
The plugin was built with extension in mind. You should be able to extend/override any feature in your project.
Please feel free to open a ticket here https://github.com/CakeDC/users/issues if you find something we could improve.
Thanks,