I'm using Redmine 2.1.2 and I want to create a link from an Issue to a file in the repository.
In the wiki I can do this very easily by source:path/to/file. But this doesn't work in the Issues.
Create Custom field of Link format
Set it's name (ex. 'Repository link')
Set URL feld as /redmine/projects/%project_id%/repository/show/%value% (for syntax look here - http://www.redmine.org/projects/redmine/wiki/RedmineCustomFields)
Related
I was trying to upload an image using Sitecore [Version 6.5] media library to my existing sitecore website. I see the Advance Upload Files option is completly missing. Later, I tried to install a default sitecore instance and I see the Advanced Upload option is there. But it is completely missing to the existing sitecore website.
Here, is the snapshot of my site where the Advanced upload option is completely missing:
And here is the snapshot of my default sitecore site where the Advanced upload option is there:
To fix this, I tried to change couple of configuration files. But still the same issue. The Advanced upload files option is completely missing. Did you face the same type of issue or if you know how to fix this issue, can you please share your thoughts. Or if I need to change any of the configuration files, then can you share your thoughts about that change of any of the configuration file?
Thanks
Upload files (Advanced) button is hidden in 2 cases:
Folder does not use Media Folder template. Just check your folders - maybe they use standard Folder template instead of Media Folder.
Upload.Classic setting is set to false. Open /sitecore/admin/showconfig.aspx and look for Upload.Classic value. When it's set to true, Sitecore uses flash upload instead.
If none of above is the case, maybe you have some custom code which hides Upload files (Advanced) button from you editors.
I created a custom module in vtiger crm version 6.5. The module was created successfully but the problem is when I click the module name a blank page appears in the view=List page.
I put the contents of vtiger version folder to module folder also language folder and change file name and class name with my module name, but how can I create view model action files according to our need?
I found some interesting tutorial in making entity module this is the link. http://community.vtiger.com/help/vtigercrm/developers/extensions/examples/entity-module.html and it is working. can you please use it
You can also create module from command line using below steps:
open the cmd prompt, go to the vtlib/tools folder and execute the Console.php file:
>cd {YourPathToCRM}/vtlib/tools
>php -f console.php
After run the command you get steps for creating various things for your CRM:
Welcome to vTigercrm Creator.
This tool will enable you to get started with developing extensions with ease.
Have a good time. Press CTRL+C to "quit".
Choose the options below:
1. Create New Module.
2. Create New Layout.
3. Create New Language Pack.
4. Create Test Language Pack.
5. Import Module.
6. Update Module.
7. Remove Module.
Enter your choice:
Use technical documentation for create new vTiger modules:
https://www.vtiger.com/products/crm/help/5.2.0/VtigerCRM_5.2.0_Vtlib.pdf
I'm using fossil to manage some home projects and keeping notes in the wiki. After running like this for a few months, I'd like to at least try to use embedded documentation; mainly so as to be able easily to go back to previous versions.
I've studied the website page about managing project documentation which confirms that this is a technique I want to follow up, but I can't make out how to do it.
I've cut-and-pasted one of my wiki pages and added it to my fossil repo, but I can't work out where it should go in the directory structure to be accessible as described on the above page.
I've tried in a few places none of which worked. The document is currently %fossil-root%\doc\foo.wiki, (I'm on Windows), where %fossil-root% is the directory holding _ _FOSSIL__ (slighly mangled filename because of markdown), but having started a server with fossil ui, when I point my browser at http://localhost:8080/doc/foo.wiki, fossil presents me with a nicely formatted page saying it can't find index.html. I created /doc/index.html to see what would happen, but it made no difference.
Please can someone help me out, and/or point me to an example repository containing embedded documentation or another "how-to" document.
If your document is located in %fossil-root%\doc\foo.wiki, you can access it at the following URL:
http://localhost:8080/doc/trunk/doc/foo.wiki
This URL breaks down as follows:
http://localhost:8080 is the root URL to access Fossil when you run fossil ui
/doc signals that you want to access embedded documentation
/trunk indicates the checkin containing the documentation you wish to access
/doc/foo.wiki is the path of the document inside the repository
Instead of trunk, you can also specify a tag, or a branch name, or even a hexadecimal checkin identifier.
In the URL you were using, http://localhost:8080/doc/foo.wiki, foo.wiki is interpreted as the checkin name, and no document path is specified, which logically means Fossil won't find anything.
As for an example repository containing embedded documentation, the homepage of the Fossil website itself is a prime example:
https://www.fossil-scm.org/index.html/doc/trunk/www/index.wiki
where
https://www.fossil-scm.org/index.html is Fossil's root URL
/doc indicates a request for embedded documentation
/trunk indicates we want to fetch files from the trunk
/www/ is the path to the requested file inside the repository
index.wiki is the name of the file inside the repository.
So, in the 'trunk' branch of the repository, the file www/index.wiki contains the home page of the Fossil website.
You simply need to put the documentation under the %fossil-root%\www\ directory (or any other directory under version control) in your repository and then you can, for example, add the following line to your header's mainmenu section to link to it:
html "<a href='$home/doc/trunk/www/foo.wiki'>Documentation</a>\n"
As I said, it can be any directory under version control. To test this, pick any file in the repository, let's say a README file at the top level, and go to http://localhost:8080/doc/trunk/README. You should see the README file load up in your browser in a raw text format. By putting wiki or html files under a particular directory such as www you make it easy to organize the files that you specifically want rendered as documentation, which makes it easier to link to them.
http://www.fossil-scm.org/index.html/doc/trunk/www/embeddeddoc.wiki
After fossil 1.33, just prepare your document in the repository.
If the wiki file is put in
/doc/index.wiki
And use web browser to setup -> Admin -> Configuration.
There is a "Index Page" field, fill in your main index.html.
For example:
/doc/trunk/doc/index.wiki
Or if you just want the released version:
/doc/<version>/doc/index.wiki
I have downloaded http://www.djangosnippets.org/snippets/1289/ for breadcrumbs, how to configure it in the application ? i.e. where to place the file and any configuration changes ?
You're likely very new to Django, so you may have a bit of reading to catch up on.
The snippet you linked to is basically a tag library. You can read about how to create and use Django tag libraries in the official docs.
For what it's worth, I would put my tag library in a tags.py file in a Django app.
I'm trying to use stapling to customize sharepoint 2010 blog template. I created a stapling feature and another feature for customizing the the site definition (onet.xml). It's work fine for web parts but if I include List Views it gives an error when I'm trying to activate the "customizing feature" (Not the stapling feature)
Error is,
"Error occurred in deployment step 'Activate Features': Cannot complete this action."
This is the xml snippet which causes this problem. (I couldn't post the xml part here)
http://social.msdn.microsoft.com/Forums/en/sharepoint2010programming/thread/6ba343f3-020b-47e5-938c-aeedcf094adc
BTW I'm trying to customize the default page here and my approach is
1) Get a copy of the existing custom page and rename and include in the feature
2) Change the master page of the above file to custom.master
3) Change the layout of the above page without removing "ContentPlaceHolders"
4) In feature element put module element copied from onet.xml
Appreciate if anyone can provide some insite on this.
Thanks
-Madhawa
Try provisioning the file without the View to make sure that your Url and Path attributes are correct. Once an empty page is displaying, add the View XML back. For the List attribute, try using the relative URL path (ex. Lists/Blog) instead of the template ID.