SugarCRM CE 6.5.11 Detail Views Broken - sugarcrm

We are working with SugarCRM CE 6.5.11. We created come custom fields within the Contacts and Accounts modules and imported some data. Now we can't access the Detail View of any of those modules.
We can create, for example, a new Lead and after creation the Detail View appears as usual.
However, once we go back to the Leads List View and click on a new Lead to see the detail view, we get nothing. We can only see the top menu and the SugarCRM footer. In Internet Explorer, it shows "null."
This happens for any Detail View within Accounts, Leads and Contacts. We can create new ones and see the list, but there's no way to access the detail view. We also tried doing a quick fix from the repair menu with no luck.
Any ideas what can be broken?

Related

Adding custom modules to activities button

I have an installation of Sugar 6.5. I'v created a custom module and created the relationship with Opportunities and I'm seeing it correctly as a panel at the bottom of the Opportunity.
I want to add it as an Activity to the "Create Task/Schedule Meeting/Log a call" button in the Activities panel.
I've tried to create a relationship with Activities but this doesn't seem to do it either. I've also looked through the dropdowns list and can't find this button/dropdown at all.
Is it possible to add options to this activity dropdown button?

Nav Bar on form issue

I am having an issue with a custom nav bar item in a form that links to a simple html web resource, for some reason the nav item is only visible to system admins, when I try to view the form with a regular user the nav item is not visible. Is there a privilege somewhere that I am missing? The nav item is in the common section of the form and it links to a web resource in CRM, I already tested and the resource is accessible to the users that cannot see the Nav item.
Download the sitemapeditor from codeplex. You probably need to give certain user rigths to do this. Using the sitemapeditor makes it that you can see how to do this by checking other nodes in the tree. Succes

Wordpress - Show Portfolio Categories

I'm working with a WordPress website and a client wants to show a list of categories in the footer. Unfortunately, it is showing as empty because he has no posts and has set the categories to portfolio items which he wants people to be able to click to.
So, how do I show the portfolio categories in the widget rather than the post categories?
Thanks,
Jack
Probably the easiest way I can think of to get the result that you want without having to resort to changing any Theme Files would be this:
Log into your Wordpress Dashboard
Navigate to Appearance->Menus
Create a new Menu, and (if applicable) enable the Custom Taxonomies for your menu by clicking on Screen Options (top right-hand corner of the page) and ticking your Portfolio's Custom Categories and/or Custom Post Types
Once all of the items you want is in your Custom Menu, save it.
Navigate to Appearance->Widgets
Add the Custom Menu Widget to the sidebar in which you would like your items to appear
Select the Custom Menu you just created, and Save
When dealing with Premium Themes, it would always be safest to stay out of their code and avoid changing anything altogether, so try this approach first. Otherwise, you may have to get your hands dirty and alter some code or contact the Theme Developer.

Need architecture direction

I'm creating an app and I need some help with design.
Launch Screen - I want to show 6-8 "category" buttons with labels loaded from an array ("normal" buttons from interface builder - not tab bar buttons or menu bar buttons).
Table Screen - When one of the category buttons is pushed on the launch screen, I want to show a table view with all of the items in that category.
Detail Screen - When one of the items on the table screen is selected, go to a new screen with details for the item. There will be an action button on this screen which will remove the item from the list if pressed.
My questions are as follows:
1) I don't want to show navigation buttons on the first screen. Can I still use a Navigation-Based application and hide the navigation controls on the first screen, or would it be better (easier) to create a view-based application and put a navigation controller "inside" one of the views? I'm totally open to any basic design approach suggestions you may have.
2) I've figured out how to create a sqlite3 file, add it to the project, query it, and generate the table view from the results, but I'm not sure about how to store the sqlite file in a way that will persist on the device when the user upgrades the app later. Any pointers on that?
Thanks for any help/links/documentation you can point me to. I've watched a million tutorials but none of the ones I've seen really address basic app design.
Now for Q1, both ways work fine but if you have buttons from the first screen, having a uinavigationcontroller might make it slightly easier if you plan to have back buttons on the screens after the first screen.
For Q2, to make the database persist when the user updates their app at some stage, simply keep the original database and include a new database (with a different name) with additional content, then modify your original database and import any additional content to it.
You can also do variations of that also, ie import content from old database to new database and etc. But the key is to keep the database file names different, ie add database_v1.sqlite, database_v2.sqlite and etc.
BTW don't forget to clean up any databases you won't use in future.

Sharepoint: Only view user created items in a custom list

I have Sharepoint 2007 Standard and am using a Custom List to create a simple form. I only want all the users to view thier own created items in the list.
If you go to your lists settings, scroll right down to the bottom and create a view, in the view you will find a section called "filter" select "Created By" is equal to "[Me]"
A better solution is to go into list settings/advanced settings and set the item level permissions. If you just change the view someone could still access the item through another channel.