I gave this plugin (P4Report) a go as recommended here and it works beautifully, I set up ODBC Data Sources properly and its bringing all the right fields across.
My main problem seems to be it not properly importing a "Description" string field and shortening it to less than 50 characters making the whole table pointless as the change descriptions are not being shown fully.
Tried importing into both Access and Excel 2013, both have the same issue.
Doubled checked and got my colleague to look with me that I had setup everything correctly and still wont fully show the description column.
Would be really nice having this working to help create patch notes.
Thanks in advance!
When you set up your query, under "changes" add "p4options". For p4options, add equals "longdesc" to add the long description.
The query will take longer to load, but it will pull over a longer description.
Related
I am very new to TOSCA and I don't have a lot of help around me for it, online searches do not seem to answer my question either.
I have scanned a basket page for a website and wish to create a loop to increase the quantity of a single product, but I can't seem to be able to read the quantity already in there, only change it. Is there a way to do this?
I am fine with conditions and loops its just this part of extracting the value from the text box.
Thank you for any help you can give.
You should be able to get the value from a text box by using the action mode buffer.
Here is the according section of the manual.
I need to change the date that Alfresco shows in the content detail. Every time I change something about properties or tags, the modified date updates to that time. That is great so far.
Problem: I need to make some changes on some uploaded files without updating that date. Some of them have their modified date changed already.
If I could set in mysql the date I wanted, then everything would be great, but if I set the audit_created and audit_modified fields in alf_node table, the change seems to affect only to the list view, but it does not changes dates in the detail view.
I've tried several workarounds of my own, but none of them has worked. Could somebody give me a hint on how to get this done?
Thanks.
Alfresco Community - v3.2.0
Not sure about version 3.2 (caugh), but I guess
behaviourFilter.disableBehaviour(nodeRef, ContentModel.ASPECT_AUDITABLE);
should do the trick. Also not quite sure at what event the behavior fires. Call this method right before you change properties.
Thanks to you all. Rebuilding the index is what actually worked for me. #Lista, I would accept your comment as answer if I knew how to do it.
I have been documenting some C++ codes (or can be any codes) over the past few months on wordpress, with the Syntax-highlighter-evolved plugin. Everything had worked fine. e.g. the C++ codes displayed correctly in post. e.g. the following syntax would display C++ codes nicely in wordpress.
[code language="cpp"]
c++ codes goes here...
[/code]
Recently, I have started exploring using mark-down in wordpress and started writing mark-down in new posts with the wp-markdown plugin. (For the benefits of simplicity and ease of migration / sharing / maintenance in long term).
... And then ... I realized all of my older posts (with codes wraped in the Syntax-highligher-evolved syntax) have all got corrupted!
For example, characters (like < > etc), got converted into HTML entities (like < > etc). In addition, I also see LOADS of HTML tags being inserted into the C++ codes.
See here for a sample post on my wordpress site (scroll down to and you will see some code blocks.). It contains some supposingly C++ codes which now looks nothing like C++ codes.
Following discovering this error I have attempted playing around with activating and deactiving the plugins to see if I could get back to the working state (i.e. codes being displayed as C++ codes, instead of hybrid C++/HTML code). No luck so far.
(Currently I have both syntax-highlighter-evoled and wp-markdown plugins activated).
Has anyone encountered similar problems before and how did you resolve this?
Would be very grateful for all the help!
UPDATES (Monday 2nd March 2015):
As a workaround I have (1) disabled the wp-markdown plugin. (2) Kept the syntax-highlighter-evolved activated. (3) Activated the Jetpack markdown plugin. The manual workaround steps below helped me correct 1 (out of about 100) posts.
It looks like the Jetpack markdown plugin complement better with the syntax-highlighter-evolved plugin. (based on my observations so far.)
As an experiment, I have modified manually an old post by (1) turning the wordpress visual editor off. (2) edited that old post. Here are the new vs old.
when I started editing the old post, I noticed that the entire post was converted automatically to mark-down format in the editor (which is good). The good news was, the unexpected HTML tag now had gone away (I presume because I was using the bare minimum wordpress editor, instead of the visual editor). So at least I could recover / copy the entire chunk of markdown-like post to a text editor (like sublime text on my desktop).
This conversion was not perfect however - I noticed some by-products. such as...
lots of carriage return (i.e. new line) disappeared - causing multiple lines got "merged" into one line. I had to manually spot for these lines and re-format them one-by-one. (a pain!)
I noticed also things like #include appeared as # include (added space in the middle). So I had to manually correct those. Likewise for some other entities containing #.
To manually edit the old (now semi-markdown) post, I removed all the legacy syntax-highlighter open tag [code language="cpp"] to three back-tick plus the code extension (```.cpp). And the close tag [/code] to three back-tick (```). See the Jetpack Markdown Doc and Markdown Extra Doc for more info.
Once updated post with the new Jetpack markdown syntax, the syntax-highlighter-evolved seemed to "know" about these new tag and automatically apply c++ color coding to it. (if I use three back-tick without the code extension, the syntax-highlighter still work to wrap the code into a block, just without the color).
Net net. The good news is that I have found a workaround which will enable me to "upgrade" the post one-by-one, manually (and a way to recover old posts - i.e. no more unexpected HTML tags in code by disabling the wordpress visual editor). Downside: this will be a lengthy process as I will have to manually spot for the missing carriage-return and re-add them to the code block. Updating 100 posts like this will take... some time.
Update (7th March 2015)
Realized that the WP-plugin actually corrupt the original blog post files. So as a quick fix I manually edited the 100 posts using the editor, and replaced all the damaged code with the corrected version. Took me 3 days solid to do but at least corrected.
I noticed that the Jetpack Markdown Plugin and/or the Syntax Highliter Evolved are not perfected. e.g. even wraping a code with the opening and closing code tags, some bugs remained - such as backslashes got stripped, the less-than / greater than signs not displayed as expected, etc.
So I for creating new posts, I have tried out the (Github) Gist in conjunction with oEmbed Gist plugins (as suggested by #OllieJones below). Works beautifully so far (Gist seem to display codes as expected. Time will tell). I have this feeling that going forward I can use Gist to store all of my blog posts in markdown files, and simply use Wordpress to "display" these markdown files. (I wonder if Gist can be used to store the image files as well? Or I need to stick to Wordpress to store the image files?).
Here are some sample new blog posts using the Gist method. example1, example2.
The doggone markdown plugin translates posts from HTML to markdown when it loads them for editing, and translates them back when you Update them. I've had the same problem with code getting trashed. This is a big pain. (I fixed it with a backup.)
My solution is to use gists -- on http://gist.github.com/ -- to display my code. The oEmbed Gist plugin makes that work very well.
Sorry I am to late.
You can edit the "SyntaxHighlighter" plugin.
open "SyntaxHighlighter" plugin, edit it
wordpress will open syntaxhighlighter.php
search and romove all "htmlspecialchars" and "htmlspecialchars_decode" string.(maybe you need backup it)
save it
I used this fixed success.
My Englist is bad, but I tried my best, hope that may help for you
Expanding on Pea3nut answer, I had to modify the PHP file for SyntaxHighlighter Evolved so it ended like this
Go to Plugins -> Plugin file editor -> Select SyntaxHighlighter Evolved on the top right -> Copy the gist in the link above -> Select all and paste it there (replace it)
This also fixes the issue with Divi, so you don't have to pay for the Divi syntax highlighter code plugin and save $9 (it's free)
When I copy a content from Ms Word and Paste to Rad Editor it works fine first time by showing a pop up and asking me whether I want to strip formatting. But on subsequent pastes to the same Editor or other RadEditors in the same page requires Pasting twice. (ie: Pressing Ctrl+V twice).
How can I solve this issue. I'm using a very basic RadEditor. nothing fancy.
Is this a know issue of RadEditor?
Try setting the StripFormattingOptions property to "MSWord" and test. If the problem still persists upgrade to the latest and greatest build of the Telerik.Web.UI.dll.
I'm using Data Dynamics Active Reports to generate some reports on our website.
Action: User runs a report on user accounts (this contains an email field) and Exports to an excel file.
Issue: If the email is relatively long, extra white space is added in the field.
Has anyone else had this problem? If so, what did you do to fix it?
Here, I found a solution to hide blank sub report space:
Add group header and footer
Check the condition
Make Group header or footer visible false/true
After some research with DataDynamics and GrapCity I found that this is a known bug they are working on Case 00023478.
To work around it I made the TextBox larger that the email fields were bound to. It's a sucky work around but it's all we have until they fix this issue.
The issue has to do with wrapped text in a texbox that forces line breaks in the excel export.
EDIT:
The better, but still sucky, workaround is to make all of your textboxes alignment "Justify". This removes all the spaces from the text on export to excel no matter what size the box, but everything is now justified...