Closed Bug 485467 Opened 17 years ago Closed 13 years ago

Table not displayed with Wordpress backend

Categories

(Core :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: dmathews, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729) After upgrading a website to the latest version of Wordpress (ver 2.7.1), I noticed a plugin (AdSense Manager ver 3.2.13) that normally displays a table of information, doesn't display the table anymore. However, I can view the table in other browsers such as Google Chrome, Opera, and IE6. Reproducible: Always Steps to Reproduce: 1. From the backend of your website using Wordpress, install the AdSense manager 3.2.13 plugin 2. Click on 'Ad Units' 3. Click on 'Create an Ad' and create a dummy one. The click on 'Show Ad'. A table that would display your dummy ad is not displayed. Expected Results: Firefox should display the results of existing AdSense contents.
Keywords: css-moz, html4
Please attach a minimized html testcase or we can't do anything with this report
Keywords: css-moz, html4
Product: Firefox → Core
QA Contact: general → general
Please close the bug WORKSFORME if you no longer see the problem when using a current version. Or, if you do see the problem, please comment with details.
Whiteboard: [closeme 2012-07-15]
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2012-07-15]
(In reply to Phoenix from comment #3) > Resolved per whiteboard That is an unhelpful, cryptical comment that requires knowing what a "whiteboard" in Bugzilla is. "Closing as INCOMPLETE because reporter provided no feedback to the question asked in a previous comment" would be helpful at least, plus maybe "please reopen if you can answer the question and if this still happens in a recent, supported version".
You need to log in before you can comment on or make changes to this bug.