During creation of new elements in EA i tried to set the element position using Element.TreePos but after setting this still the element in EA is getting inserted based on the Alphabetical order. But once the project is reloaded it is getting arranged properly as per the TreePos.
EA.Element mobjElement= mobjParentelement.AddNew("","Requirement");
mobjElement.Name= "Sample";
mobjElement.TreePos=1;
mobjElement.Update();
You have to reload before a change in TreePos becomes apparent.
You can use EA.Repository.RefreshModelView(long PackageID). According to the documentation the PackageID parameter should limit the reload to only the package with the given ID, but I have not found a difference between reloading a single package or reloading the whole model (using 0 as parameter).
Since v13 there is also EA.Repository.ReloadPackage(long PackageID) which might do what you need, but I haven't tested that myself. From the documentation it is not clear what the exact difference is between the two operations.
Related
I want to render a absolute link in table from value of cell but I got a relative link instead.
Here is my configuration:
What I got when click on cell:
http://10.93.9.209:3000/http%3A%2F%2F10.131.227.253%2Fjob%2FPerformance%20Testing%20Pipeline%2Fjob%2Fstable%2F21%2F
In Grafana 7 (new table panel) it's ${__data.fields[2]} where number is column index.
This is a change introduced in one of the new Grafana versions. If you want an absolute URL, you must use ${__cell:raw} instead of ${__cell}. Reference
If you want to reference another column when clicking:
This is possible, I am using 9.1.7 and originally used the old table; however, after migrating noticed the same issue. That said, I found a way to make this work:
Add the ID column that you want to hide; example simID
If the column is the first column, say 0; then use:
var-whatever=${__data.fields[0]}
Now, override the column, field with name: simID Add option ‘Hide in Table’ and turn on
I also had to format the number, e.g. remove decimals & set unit to standard
Hope that helps someone… took me a good 2 hours to figure.
Btw, it also works on graphs and you do not have to hide; aka reference your original query in the datasource and add a data link with the same options.
What result do you get if you try $__cell_2?
The syntax above no longer works. The value is now ${__value:raw}
$__cell_2 above solution worked for me.
With the new table panel introduced in Grafana either ${__cell} or ${__cell:raw} do not work for this now.
You must use ${__value:raw}
Since updating from Flux 6.0.2 to the newest Flux TER-Release (7.0.0) I have the problem that all my defined flux:field.select items are switched. I have them defined as an array like this items="{0: {0: 'value shown as a CSS class in the frontend',1: 'value shown in BE'},}". But now I get the BE value in the frontend template.
Also all my content elements from my provider extension are shown twice (without a title) in the backend and the fields defined in the 'Configuration' section of my content element are shown twice.
There's also a RTE field shown at the bottom of my content element that has not been there before.
BE Output: view
Code on Pastebin: http://pastebin.com/CNcphn2k
Any help deeply appreciated.
EDIT:
I just set up a fresh instance of TYPO3 6.1.9 (blank package) and installed my extension with the above mentioned content elements. Dependencies were resolved automatically as it should (newest versions). Via the content wizard I tried to create a new element and I get the same result as in my existing install I first noticed this bug in.
EDIT2:
I was able to narrow it down to the flux:form.container tag. This duplicates the output in the BE. The select values are still switched though.
It is possible that you missed this official announcement:
http://fluidtypo3.org/blog/news/new-colpos-value.html
Failure to run the update script before letting TYPO3 change the type of the colPos value will result in the symptoms you describe. There is, unfortunately, no way to restore this (since your SQL will have cropped off all negative values and made them zero without any backup).
Restore from a backup and run the script and you should be fine.
If I open the extension manager, switch to the tab Import Extensions and select the filter I get the following options:
Display all extensions (empty)
Only display installed extensions (working)
There should also be a Only display updatable extensions selection but this isn't displayed. What is the reason therefore?
I made a TYPO3 update to 4.7.2 and perhaps thats the reason why it isn't correctly displayed?
The repository is up to date.
The filter has been moved from the Import Extensions to the Available Extensions tab.
You do not actually want to import an extension, but update an existing one.
Just suggestion: I had similar issues with button displaying in EM before (4.6.x) (ie. Install ext button) and realised, that the button is available, but sprite image had wrong position which caused that the button was transparent,
Try to use ie FireBug to check it, and eventually fix the CSS (and report the bug)
Edit:
Some doom apparently, I just had identical situation just seconds ago ;) Fortunately found the reason: the ext list is displayed with ExtJS grid, which can contain custom filtering per column. Literally: when you for an example click on the column's dropdown arrow, you can in its filter set some value to narrow the search results.
Ie.: in the main filter field write news and additionally in the Extension Key column set other filter tt_news. (if you want to display only %tt_news% in result list of %news%)
In that case even if you'll clear the main filter, the one set on the column will stay active, so next time when you'll try to search for realurl in main filter, it will return empty list as Extension Key filter is still set to tt_news.
Weeeird, however helped me :)
You can recognize filtered columns as their names are written with cursive, finally you can just check every column and disable any filtering on each.
I am stumped beyond belief.
I have a select box being generated by the cakephp form helper. I am feeding it an array of options, and passing an empty value... pretty standard stuff.
However, my "empty" field is showing up at the very bottom of the list.. not the top. So when the field loads, it just defaults to the first option... which is not the "empty" option.
Not a whole lot of room for error on the code here..
echo $this->Form->input('whatever',array('empty'=>'Choose One','options'=>$categories));
The only small item that might be important, is that $categories is a multi-array, so the select box has optgroups & options.
Is there some quirk/bug out there that I do not know of that is trying to force me to sneak into my scotch supply a few hours ahead of schedule?
edit: using the latest release of cakephp 1.3.x
I think that I once had the same problem.
It turned out to be the data (options array).
Is there an option with an empty key? probably the last one then.
this lead to the scenario I remember and seems to be the exact same thing.
the form helper will override this empty key value pair then and not create a second one.
without more infos from your end this will be difficult to solve.
Is there a way to display {children} in a table in a way that they all sit withing a column, one per row?
Say, I have subpages a, b and c, and want them show in a table with page name, author and something else:
|a|Denis|40|
|b|Alex|43|
|c|Unknown|2|
Did you try the reporting plugin
checkout
http://wiki.customware.net/repository/display/AtlassianPlugins/Reporting+Plugin
for instance use following config
{report-table}
{local-reporter:page:children}
{text-sort:page:title}
{local-reporter}
{report-column:title=Title}{report-info:page:title}{report-column}
{report-column:title=Author}{report-info:page:creator}{report-column}
{report-table}
Quite a bit of fun using it, once that you get going.
Francis
You could also use {metadata-report}
{metadata-report:Page,Author}
{metadata-report} is used to display metadata stored on pages using the Metadata plugin and can also be used to dislay content properties including: Page,Author,Last Changed By,Last Time Changed,Date,Time,Time Created,Posted,Space,Parent
You can also set the root page to start from and pull all of the basic page metadata out into a table. Example:
{metadata-report:Page,Author,Last Changed By,Last Time Changed,Date,Time,Time Created,Posted,Space,Parent|root=somepagewithchildren|pages=#descendants}
This can be wrapped in {table-filter} and {table-plus} macros for sorting.
{table-filter:userfilter=Page,Author,Time Created}
{table-plus:columnTypes=S,S,D"dd MMM, yyyy hh:mm"}
{metadata-report:Page,Author,Time Created}
{table-plus}
{table-filter}