In this document are reported PHP Analytics’ known issues.  The following issues do not affect the main software execution, anyway they have been identified as mandatory fixes for future releases.

Backend issues

Issue #B1 – Connection/Query modification affects views.

Description:  This is obvious; if you delete a connection, the related query cannot be executed  and the related view will result empty. Similarly, if you modify a query and the new related resultset is different in column number, order and types from the previous one, view’s columns metadata could not match anymore with the new ones.

Workaround: whenever you modify consistently a connection or a query, please consider that you have to rebuild the views from scratch or at least modify the metadata in the database (not recommended).

Issue #B2 – Empty result set with ambiguous column’s names.

Description:  When testing a query that has the same name for different columns an empty resultset is returned.

Workaround: assign a column alias in order to resolve the ambiguities.

Issue #B3 – TinyMCE plugins don’t work anymore from WordPress version 3.0.1.

Description:  When opening the dialog box to import in your page/post the table or chart views previously created, you cannot see the created views, but just the same page with in the dialog box.

Workaround: you have to write manually the metacode for the view you want to import.
E.g.: [phpanalytics id=”1″ type=”chart” iframe=”no”]MyChart[/phpanalytics]

Frontend issues

Issue #F1 – iFrame option for table view does not resize automatically in IExplorer.

Description:  whenever a table view is marked to be published within an iframe, the iframe itself need to adapt dinamically is size depending on the table content. This worth both during the first page load and during the table data navigation (only for paginated table views). In order to resize automatically the table, PHP Analytics uses the jQuery iframe Auto Height plugin. Currently, when using IExplorer, the iframe is not resized even during tha page load.

Workaround: even if the iFrame option is provided, PHP Analytics does not recommend it. The iFrame option has been provided as a fast solution to avoid CSS propagation: usually WordPress templates include CSS styles for HTML tables; sometimes these properties affect the custom CSS style associated to a particular table view. In order to avoid that you need to modify (or better eliminate) all the occurrencies in you WordPress default template CSS files that affect table’ styles.

Issue #F2 – Column header names allow special character.

Description:  the script that avoid the user to type special characters within the column name textboxes do not work.

Workaround: do not type special characters within the column name texboxes to do not get strange results.

Issue #F3 – Flash chart preview appears at the bottom of the page when closing dialogbox with X button.

Description:  when you add a chart by using the tinymce_phpanalytics_chart plugin a dialog box opens. If you close the dialog by clicking the X button in the top-right window corner, a chart preview appears at the bottom of the page.

Workaround: Need to find a way to trigger a jQuery(‘#chart-preview’).hide() on dialog box closing.

Issue #F4 – Flash chart preview doesn’t work in Internet Explorer 8.

Description:  when you add a chart by using the tinymce_phpanalytics_chart plugin a dialog box opens. When you choose one chart from the menu list, a preview should appear but it doesn’t in IE8. This doesn’t affect the main functionality.

Workaround: Need to find the reason of the issue.

Issue #F5 – Table and Chart TinyMCE plugins add metacode on top of the page.

Description:  when you add a new chart or table via PHP Analytics’ TinyMCE plugins, metacode is inserted on top of the page.

Workaround: Need to find a way to append metacode starting from the cursor’s current position.