Hy Guys,
In SugarCRM 6 there is an attribute in config.php file named default_module which indicates that after a user gets logged in successfull he will be redirected to that specified module. For example if i have mentioned Contacts as the default module then the user will see the Contacts module as his first module (in other words the landing page become Contacts list view) after getting loged-in instead of the standard Home module.
But this parameter is not working in SugarCRM 7.
Any ideas hows to implement this logic in an upgrade safe way in SugarCRM 7. One of the possibilities that comes to my mind is to make a redirect in after_login logic hook to a specified module.
Can you give me any other options/ideas that can be implemented in this scenario?
Related
I am right now using LDAP authentication for adding user in Suitecrm. In normal course when the user is added to the system we can assign him roles during creation and also hide some modules which are enabled for him, in his portal .
With LDAP authentication I have been able to assign user to a role through code when he first logins but hiding modules for those users by code or otherwise has not been possible
Can anyone guide me as to how to hide modules from the current user which otherwise show in the navigation bar?
Thanks in advance.
There is upgrade safe manner to do it via smarty file.
Check your active theme and copy the file from themes/<active_theme>/tpls/_headerModuleList.tpl to custom/themes/<active_theme>/tpls/_headerModuleList.tpl (if custom directory doesn't exist then create it)
Search for groupTabs, you will see foreach loops for processing it for different views. Hopefully, you can add your code there to do anything.
I'm looking to create a customized contact form in a Joomla 3 site I have created. I know how to write the php code for the form, but I'm unsure of where to place the code.
Ok, the form is located at http://www.theoscorner.com/contact-us. What you see there is only the design, and there is currently no script for the form to submit to. If I wanted to create a new php page for the form to submit to, what is the best method of doing this? For example:
Should I create a completely new php file where the template's index.php file sits, and use a module (instead of an article) to hold the form.
Should I create a new article page, and place my php script in that article?
Should I hard-code my form into a module, and place a php function at the end of the index.php page which gets called when the page is refreshed and the POST values are set.
I'm just looking for any type of guidance I can get right now. I don't want to use a third-party plugin, because I want a little more control than they allow. Thank you for your time.
Just use RS Forms or Contact Enhanced, they are both Joomla extensions available on extensions.joomla.org
There is no need to create your own MVC component.
Multiple stores in Magento 1.7.
I am having issues setting this up.
I have set up via configuration two websites, store, store views etc and the url's in web config.
I have changed the A records on the domain to point to the magento website and I have as instructed changed index.php but when i type in my 2nd website address it just takes me to the main (original) website pages, if I change the default website in Magento it works! I can't be far off but I'm struggling now, any advice?
I've been told that in 1.7 I only need to alter index.php to make it work
Andrew
you must provide either store code or website code to server variable $_SERVER['MAGE_RUN_CODE'] or as first parameter to Mage::run() function in index.php file, for example if every subdomain of site has one store, you can accomplish this by:
$storeOrWebsiteCode = strtok($_SERVER['HTTP_HOST'],'.');
$_SERVER['MAGE_RUN_CODE'] = $storeOrWebsiteCode;
or
$storeOrWebsiteCode = strtok($_SERVER['HTTP_HOST'],'.');
Mage::run($storeOrWebsiteCode, 'website');
or
Mage::run($storeOrWebsiteCode, 'store');
I would like to create a login screen for registered members on front page of the site without using members module. As I can see I can create a member and assign login credentials at back-end ( I don't have member module). Basically the idea is:
visiting: www.domain.com will give you login screen. When logged in it will redirect you or open new page.
I'm not looking to buy a module or extension. If something already exist I will be happy to use it.
Can anyone help?
You "don't have the members module"? How is that possible - it comes with the default install! So, something does already exist - it's called the Login Form tag.
So is the question how to create a login form on the front end of the site, or how to keep non-logged in users from viewing a specific template?
If it's the latter you can set access privileges at the template level. Look for the "Access" link by each template in the Template Manager, click that and you'll see your member groups and an option for what template to display if they aren't logged in. Typically that's a login template using the Login Form tags mentioned earlier.
I am having a site as http://www.test.com running in Joomla 1.5 . We are planning to have a microsite like
http://www.sub.test.com which has to have separate homepage with different contents .
Is that is possible with the following idea
Making a export of all the tables in my joomla and replacing jos with suband again importing them into the same Joomla database.
Writing a PHP script of identifying whether the Url tat i have entered in the browser is
http://www.test.com OR
http://www.sub.test.com
If test.com, then the $dbprefix would be jos OR if sub.test.com then the $dbprefix would be sub.
Will the above idea for creating a microsite is the correct one.
Just as another option, you could contain both sites in the exact same instance with a different template assigned to the micro site.
Set up a content category for the micro site, detect the request URL (most likely in the WebServer - best location, or in a DNS setting with a forward URL)
Assign all content items in the category with the new Template.
We regularly do this for a site that wants a blog site alongside the main website, but want a different look and feel.