I am following the "Joomla! Programming" book by Mark Dexter and Louis Landry.
I came up to the point where we create a plugin to check whether both terms of service agreement and age above 18 is checked in the alternative registration form layout which we create earlier (approval.php).
When testing this plugin, I checked only one of the checkboxes and showed the "Registration Failed" error as expected. But on the error page, the registration form is the default one and not the alternative one which we created earlier (approval.php)
Why is this?
Related
For the contact entity I have set the default values for some build in fields to specific values. For example I set the default value for the field "Contact -> donotemail" to the value "Do not Allow".
In the "normal" web browser forms it seems to be working as expected.
But if I create a new contact using a quick create form and select the save and then "view created record" button the view switches to the new created contact.
If I then scroll down to the "donotemail" - field the field does not have the default value I selected in the field settings.
I googled the problem, the nearest community post I could find is
https://community.dynamics.com/crm/b/mohamedmostafacrmblog/archive/2016/06/02/set-field-default-value-in-microsoft-dynamics-crm-online-and-on-premise-using-business-rules-without-javascript-or-custom-components-plugins-or-workflows
Unfortunately the post is from 2016 and it describes how to workaround the problem using custom business rules. But due to this is build in funtionality there is no business rule I could edit and creating some new to achive the goal of setting a default value seems odd.
Did someone encounter this problem too and could find a solution?
One possible reason I could think of: you might have not refreshed the main window after publish all, maybe cached QC form didn’t work as expected bcoz “customize the system” will open a separate popup to edit & publish all.
Still technically server side should not be cached with old customizations. But QC might have rendered from cached Metadata in browser.
But publish all should reflect immediately & no delays expected. Make sure to refresh the main window next time :)
I have a public page with a data-request = onClaim button.
A user can use this button whether he is logged or not
When the user "claims" this page, if certain conditions are fulfilled, the database must be updated and then a specific restricted access page have to be displayed with the new updated datas.
If conditions are not met, user stay on the public page with warning message.
To know if these conditions are met, the user must be logged in (using his account or creating new one)
note:
When the restricted page is displayed by any other way than this button. No specific data is updated
hard to explain, do my best !
Please, How to implement this workflow elegantly (or not)?
development environment:
october 419
rainlab User plugin
debugbar 1.0.8 plugin
sweet alert 1.1.0 plugin
i tried some tricks but according to the xy problem, i prefer don't talk about
I am having issues with the following components not working as expected.
Crosstec BreezingForms
Crosstec ContentBuilder
For those of you who have used these extensions before, my issue is that the Content Builder List View will not display all submitted forms if "Create Article" in Content Template is not checked. In summations, if an article is not created the form is not listed in the frontend CB List View. The List view should pull all form submission from a BreezingForm form regardless of how it was submitted (frontend, backend, breezingform menu item) but it is not.
I have been working with Crosstec Support and they cannot explain why they are not working as expected. They say it may be caused by another extension.
I would like some assistance as to what I can do to locate the culprit extension.
Any ideas?
Thanks in advance for your help.
I am developing an NSIS package for one the products. I have a custom page for gathering SQL Server login credentials. On this page, clicking next must validate the given inputs (whether it connects to the server with given credentials). This works fine.
Problem:
If I press back button on this page, it is still validating the input; which I do not want. I could not find any way out to skip the validation on clicking back button.
Any suggestions in this regard is appreciated.
Found the answer!
We can specify two function names while calling the page custom command. One to show the page and one for validating which is called as leave page.
Page custom ShowDatabasePage LeaveDatabasePage
In the leave function, we can do all the validation. If the validation fails just call abort and the work is done. Leave function is called only when the next button is clicked.
I'm setting up a set of custom templates for a SagePay server integration (iFrame), and I'm wondering if anyone knows if it's possible to prevent the confirmation page (card_confirmation.xslt) being presented to the user.
It mostly duplicates information presents to customers earlier on in the checkout process and so is largely redundant.
So it's a bit of a long shot but can we by modifying some form value in one of the other templates or by any other method tell the system to skip that page?
Thanks.
You won't get this confirmation page if you pass Profile=LOW with the original transaction registration post. In fact, if you are not sending this and displaying the Sage Pay screens in an iframe, you are going to have problems with some browsers.