One small drawback of v1.0.1 of this plugin (current as of this writing) – if permalink URL of your post is very long (pretty ones tend to be) – it gets cut off during HelloTXT notification, since status update has to be within 140 characters length. But there’s an easy solution. Open PHP source of the plugin in any text editor and in function hellotxt_notification locate line:

$link = get_permalink($post->ID);

This is the line that gets permalink of your post. To replace it with shortened URL we can call API of TinyURL service:

$link = file_get_contents("http://tinyurl.com/api-create.php?url=".get_permalink($post->ID));

and Voila! short links are being sent to HelloTXT

most likely it’s because grid’s ItemCssClass property is used. In theory (at least according to ever so verbose documentation) it should define what grid’s cells look like. In practice it have no effect whatsoever. Or rather had no effect until upgrade (verified in version 2011.1, perhaps even earlier). Now if your CSS class used in this property contains HEIGHT attribute – a blank row of that height will be inserted on top of the grid.

Solution? Remove ItemCssClass property. It’s useless anyway.

• It was a context popup menu, called on right mouse click
• Text of menu items was assigned dynamically at runtime in JavaScript Client code

After upgrading NetAdvantage from version 2009.2 to 2011.1 strange things started to happen. Text of the menu items was cut short, submenues appeared at wrong places it looked like something from a Dali’s painting.
Numerous experiments later I found out that the problem was with EnableScrolling property of the menu control. Setting it to False returned menu to realm of realism.

Microsoft JScript runtime error: Sys.ArgumentUndefinedException: Value cannot be undefined.Parameter name: type

With ScriptManager in Release mode it’d be:

Microsoft JScript runtime error: Object expected

But always in Sys.Component.Create – it looked like grid’s client-side scripts weren’t loading at all. After A LOT of digging I found out that the culprit was grid’s server-side Bands.Clear() method. When called, it caused client-side WHDG JavaScript not to load. When that method was commented – JavaScript errors disappeared. So until Infragistics comes out with a bug fix – if you experience similar problem, try to avoid Bands.Clear() method.

Failed to connect to 2a00:1450:8006::63: Network is unreachable

Note the IPv6. Google have been supporting it for a while and news.google.com resolves to IPv6 first (similar error happens in WordPress admin dashboard in “Incoming Links” section). Unfortunately network of my new host didn’t support IPv6, so I had to find solution to force WordPress to use IPv4. Enter class-http.php.

Located in /wp-includes folder of your WordPress install this module is responsible for different aspects of HTTP communication. By default class WP_Http_Curl is used. If you open function request you will notice several CURL options bein set, e.g.:

curl_setopt( $handle, CURLOPT_URL, $url);
curl_setopt( $handle, CURLOPT_RETURNTRANSFER, true );
curl_setopt( $handle, CURLOPT_SSL_VERIFYHOST, $ssl_verify );
curl_setopt( $handle, CURLOPT_SSL_VERIFYPEER, $ssl_verify );
curl_setopt( $handle, CURLOPT_USERAGENT, $r['user-agent'] );
curl_setopt( $handle, CURLOPT_MAXREDIRS, $r['redirection'] );

If you’re running PHP 5.3 and above – there’s an obvious solution, just add one more option to force IPv4 resolve:

curl_setopt( $handle, CURLOPT_IPRESOLVE, CURL_IPRESOLVE_V4);

Unfortunately my host is running PHP 5.2 and there is a known bug about missing cURL option do disable IPv6 in version prior to 5.3. Thanks guys from Google IPv6 team for finding this, when I contacted them about my IPv6 issues with Google News, they responded to emails instantly, went above and beyond call of duty and I am sure they didn’t simple Google the answer.

So, the less obvious solution is to disable CURL altogether, forcing WordPress to use other means of HTTP transfers. The class has function test to see whether CURL can be used:

function test($args = array()) {
   if ( function_exists('curl_init') && function_exists('curl_exec') )
      return apply_filters('use_curl_transport', true, $args);

   return false;
}

Comment the fist 2 lines to make function always return false:

function test($args = array()) {
   //if ( function_exists('curl_init') && function_exists('curl_exec') )
   //   return apply_filters('use_curl_transport', true, $args);

   return false;
}

This will tell WordPress that CURL is not available making it switch to other HTTP means that are not forced to use IPv6.

An error has occurred while attempting to load the Crystal Reports runtime. Either the Crystal Reports registry key permissions are insufficient, or the Crystal Reports runtime is not installed correctly. Please install the appropriate Crystal Reports redistributable (CRRedist*.msi) containing the correct version of the Crystal Reports runtime (x86, x64, or Itanium) required. Please go to http://www.businessobjects.com/support for more information.

then switch your application to 32bit mode. In case of Windows 2003/IIS6 entire server will have to be switched, in case of Windows 2008/IIS7 a dedicated 32bit application pool can be established for your application.

What is happening – PHPBB displays cached version of the template. Forum software caches commonly used files to improve performance. The solution is to purge cache.

Login to your forum Administration Control Panel and click Run Now in Purge the cache section. After purging is complete changes in your template take effect.

Me.ClientScript.RegisterStartupScript (Type,  Key,  Script, AddScriptTags)

Where

type: The type of the startup script to register.
key: The key of the startup script to register.
script: The startup script literal to register.
addScriptTags: A Boolean value indicating whether to add script tags.

For example:

Me.ClientScript.RegisterStartupScript (Me.GetType(), "alert", "alert('Hello world!');", True)

But if you’re using Infragistics controls that offer async postbacks, like WARP panel or UltraWebTab – there is a problem with this approach.  Since the page doesn’t go through the full postback and doesn’t get destroyed and re-rendered from scratch – this method doesn’t work.

One approach is to create a literal control (either static in ASPX markup or dynamic thru code) and assign it the code that needs to be executed on the client:

xltScript.text = "<script type='text/javascript'>alert('Hello world!');</script>"

It works, but it can become messy and hard to maintain.  A much better approach is to use Infragistic’s CallBackManager’s AddScriptBlock method:

AddScriptBlock(page, ownerOfAsyncPostBack, javaScript)

Where

page: Reference to Page.
ownerOfAsyncPostBack: Control, caused async postback. If that parameter is Nothing, then script is added regardless of the owner of postback.
javaScript: Javascript statements.

For example:

Infragistics.WebUI.Shared.CallBackManager.AddScriptBlock(Me, Nothing, "alert('Hello World!');")

To make it universal we can combine both original ASP.NET approach for full postback and the Infragistics method for async postback into a single function:

Public Sub RunJavascript(ByVal i_oPage As Page, ByVal i_sJScode As String)
   If Infragistics.WebUI.Shared.CallBackManager.IsAsyncPostBack(i_oPage) Then
      Infragistics.WebUI.Shared.CallBackManager.AddScriptBlock(i_oPage, Nothing, i_sJScode)
   Else
      i_oPage.ClientScript.RegisterStartupScript(i_oPage.GetType, "JSCode" & Rnd(1).ToString, i_sJScode, True)
   End If
End Sub

Here, the function RunJavascript (which can reside in a standalone class, separate from the page) accepts 2 parameters: the reference to ASP.NET page and the string with JavaScript statements. First it checks whether the page is in async postback mode (Line 2, IsAsyncPostBack method) and if so – performs Infragistics AddScriptBlock method. Otherwise it peforms standard ASP.NET RegisterStartupScript method (note randomizer used for the key parameter, this is done so if you call this method several times in a row, all JavaScript statements will added, otherwise only the last one will remain).

Therefore we combine examples from above into a single call:

RunJavascript(Me, "alert('Hello world!');")

and the JavaScript code will be added to the page no matter whether it is first load, full postback or Infragistics async postback. Don’t forget to add semicolumn at the end of your JavaScript statement, in case more statements are added later on (otherwise you may get a syntax error when client script tries to execute).

function onMouseClick(oEvent) {
   if (oEvent.button == 2) { //right mouse button clicked
      var menu = $find("xwdmMyMenu");
      menu.showAt(null,null, oEvent);
   }
}

It checks whether the right mouse button was clicked (line 2) then locates the menu object and shows it using showAt method (which accepts 3 parameters, either X and Y client coordinates, or event object from which it derives coordinates of the mouse click).

 It’s all well and good, but the problem is – menu always shows down from the location of the mouse click. And if the click is at the bottom of the screen – menu gets cut off:

I needed to make menu expand UP and  couldn’t find a build-in property or method that would change this behaviour (GroupSettings.ExpandDirection property had no effect). Time for a little hack. Well, not really a hack since it is used standard public properties and methods. The solution is to shift menu location up by the hight of the menu element:

function onMouseClick(oEvent) {
   if (oEvent.button == 2) { //right mouse button clicked
      var menu = $find("xwdmMyMenu");
      menu.showAt(oEvent.clientX, oEvent.clientY - menu.get_element().clientHeight, null);
   }
}

This approach uses second variation of the showAt method that accepts X and Y coorinates. for X it takes clientX cooridnate of the mouse click. And for Y it takes clientY coordinate of the mouse click less hight of the menu element. Which creates the appearance of menu expanding up:

(Think a strategy game – you’re placing construction on the terrain – if there is enough unoccupied room – the draggable item becomes green, otherwise it remains red).

The solution is to use elemAtPoint property during DragMoveHandler event. Register the event handler during page load:

var g_ddb; //drag and drop behaviour

function pageLoad(sender, args) {
//attachng drag-move event handler
g_ddb.get_events().addDragMoveHandler(dragMoveHandler);
//some other initialization code
//...
}

and then during the drag operation when this handler is called – use elemAtPoint property to retreive HTML element:

function dragMoveHandler(sender, args) {
//getting element over which drag move is happening
var oEl = args.get_manager()._currentTarget.elemAtPoint;
//using that element
//...
}