I want to have multiple registration forms or fields depending per the type of user. I am having some of the data already stored in my database and I want that during registration, those fields should be matched. If the match is successful, then the person will be registered else not.
I request if someone can tell me about any free extension/plugin for the same or any documentation of using which I can code a module as per my requirement.
Just make a copy of the core profile plugin and change the name in the xml. THen you will be able to add different xml files and load them conditionally and in your plugin you will code whatever you want to happen using the various user events related to registering and saving.
Related
I'm wondering if Drupal allows me to attach multiple informations to an multiupload image field. F.e. copyright, creator and taxonomy references for people appearing on the picture. Is there any module that can handle these requirements? If not, where could I hook in?
Although your mileage will vary, what you're looking for is File Entity.
This module will promote files into fully fledged entities, allowing them to have fields in the same way as all other entities (eg nodes). You can then add whatever fields you'd like, from the pool of field modules you have installed.
I'm using the user profile plug in for user registration form, but I need to change the url the form get posted to when submitted.
How can I do it?
The user profile plug-in is a core plug-in that extends com_user... it doesn't control the submission of the user registration form.
If you want to modify the user profile process, then the safest way to do it would be to make a copy of the user profile plug-in, rename the relevant sections to make it your own plug-in — you probably want to start with this section on Plugins.
By modifying your own copy you will be able to keep up-to-date with Joomla's security patches because you won't have modified a core file.
If you want to modify the registration process, you would need to override com_user before doing that though I would suggest you check the Joomla! Extension Directory (JED) first. There are a large number of extensions that modify the registration process, offer integration with other systems and extend the user profile already in existence.
Another tack might be to use one of the forms extensions that also handle user registrations — typically they allow you to create all sort of custom form including replacements for the standard user registration form. We've been very happy with a few of them and currently use RSForm Pro! — it's a commercial product but extremely flexible and well supported for the small amount of cost involved.
For the record, the solution was to do a template override /html/com_users/registration/default.php and changing the action to some url specified in the template configuration:
action="<?php echo JFactory::getApplication()->getTemplate(true)->params->get('myFormAction');
I've an existing MVC3 project that implements a certain functionality, this project has it's own views, and a separate Database.
now I'm required to use the same functionality inside one of my orchard project,so I thought that I can host this solution in somewhere and view it inside an iframe or something.
Am I thinking right?,
is this the correct step to take in order to achieve this requirement inside Orchard?
to make it more clear, all I need to do is to view this solution and interact with it's controls and views from a hosting page inside orchard, and the subsequent requests should be handled by my solution in order to hit it's own data store and get back with the requested data in order to be displayed to the user.
any help would be appreciated.
Update:
thanks for Bertrand Le Roy for his answer, I can now view my solution inside my
orchard website.
I came in to one more HUGE problem, which is that my application can no longer connect to my external database.
I've a DB that is hosted in some where else, and I'm using EntityFramework to deal with it.
the problem is that if I put the connection string inside my module web.config, or main orchard web.config, I run into several types of errors like:
"System.Reflection.TargetException: Object does not match target type."
or
"System.Data.MetadataException: Unable to load the specified metadata resource."
My question is: How could I pass my connectionstring correctly to my solution, assuming that I'm using Entity framework as my ORM.
Many thanks.
You will need to put it into a module.
You will have to move route definitions to a Routes.cs file (look at any existing such file for examples).
You will also need, in order to access your data store, to opt out of the ambient Orchard transaction around the data access code (using (var scope = new TransactionScope(TransactionScopeOption.Suppress))).
If you are using dependency injection, you may have some work to move that to the Autofac-based way of doing things in Orchard.
If you want your work to appear seamlessly in the Orchard admin, you may want to decorate your admin controllers with the Admin attribute. If you want your front-end to use the current theme, you'll have to add Themed attributes and maybe refactor your views so that they only emit HTML for the content zone instead of for the whole page.
Add a manifest (module.txt) to your module folder and you should be good to go.
I'm creating a solution which will be released as a managed solution for Dynamics CRM Online.
However, the customer will need to put information in when installing the managed solution to allow interaction with outside services.
For example, when you install the LinkedIn solution, you need to add your log in information to allow the CRM to access your LinkedIn account.
How do I add these parameters to the a solution, and then allow the customer to update them if they change?
Cheers
Edit:
To add to my query and following the answer below.
To make sure the process is correct in my head.
Option 1.
I will create a custom entity for storing key/value, or username/password combination.
I would then create a customisation page for the solution using html web resource, which when submitted, javascript would create a single record to hold those values.
I then need to link every record that needs the values stored in the custom record - I'm not sure how this would be done without editing a workflow after the storage record has been created, to link each normal record to the storage one.
Option 2.
Create an xml web resource that stores the values. Create the html/javascript resources to update this using the configuration page.
I can then use a javascript function to obtain that data when the custom entity is created, perhaps to populate hidden fields for storage and use behind the scenes.
I can't find any tutorials on getting started with using xml in this way - can you point me in the right direction?
I typically create a "Configuration" entity that has Name/Value attributes. This is also useful when you have Dev/Test/Prod environments that require different configs (e.g. URLs, credentials, etc).
Another approach is to using Plug-in configurations or Web Resources to store that type of information. The Plug-in configuration is pretty straightforward if you can have the customer use the Plug-in Registration tool to modify the value.
I just finished to implement a custom functionality in one of the page articles in my Joomla website using sorcerer. In this page it is possible to query a hash and lookup it against a database.
I would like to store the last 5 queries and show them in the page but I don't know how to do it. I need something as Java EE "Application Context" to store this values and make them available to all the users so using a Session to store this values is not what I need.
I saw in the documentation that in Joomla exists JApplicacion but none of his methods allows me to store data.
Not having used Java, but I am pretty sure that the whole PHP platform has no "Application context". You simply need to store them in a database table.
JApplication is used to wrap up all the code that runs as the Joomla CMS. Its livetime nevertheless ends with the end of the request.
HTH, Jochen