Bug 3055 – New submission step 2 -- "Supporting Agencies" input field missing (caused by ad blocking software)

Bug 3055 - New submission step 2 -- "Supporting Agencies" input field missing (caused by ad blocking software)

Summary:

New submission step 2 -- "Supporting Agencies" input field missing (caused by...

Status:	NEW

Product:	OJS
Classification:	Unclassified
Component:	Authors
Version:	2.4.x
Platform:	PC Linux

Importance:	P1 enhancement
Assigned To:	PKP Support

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-10-08 08:46 PDT by Ivailo Stoyanov
Modified:	2012-09-21 17:20 PDT (History)
CC List:	1 user (show)

See Also:
Version Reported In:
Also Affects:

Attachments
Screenshot: New submission, Step 2. (112.44 KB, image/jpeg) 2007-10-08 08:49 PDT, Ivailo Stoyanov	Details
Here is the page in question saved as HTML (zipped) (88.75 KB, application/octet-stream) 2007-10-08 10:19 PDT, Ivailo Stoyanov	Details
The field in question isn't visible on my off-line copy of the page as well. (94.19 KB, image/jpeg) 2007-10-08 10:45 PDT, Ivailo Stoyanov	Details
The same page renders as expected in MSIE (6.0.2900.2180). (88.67 KB, image/jpeg) 2007-10-09 00:51 PDT, Ivailo Stoyanov	Details
... and also in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 (85.42 KB, image/jpeg) 2007-10-09 01:29 PDT, Ivailo Stoyanov	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ivailo Stoyanov 2007-10-08 08:46:12 PDT

When an author submits a paper, in step 2 (Entering the Submission's Metadata) there's no input field to specify "Supporting Agencies".

Comment 1 Ivailo Stoyanov 2007-10-08 08:49:23 PDT

Created attachment 310 [details]
Screenshot: New submission, Step 2.

Comment 2 Alec Smecher 2007-10-08 10:11:33 PDT

Thanks, Ivailo, but I'm having trouble duplicating this locally. Could you save a copy of the HTML output (e.g. using File -> Save As in your browser) and attach it here? It might also be worth checking your server log for PHP error messages.

Comment 3 Ivailo Stoyanov 2007-10-08 10:19:40 PDT

Created attachment 311 [details]
Here is the page in question saved as HTML (zipped)

Comment 4 Alec Smecher 2007-10-08 10:29:34 PDT

Hmm, that saved HTML looks exactly as it should. Have you tried reloading the page? Perhaps it was a one-off server or browser glitch. What browser are you using?

Comment 5 Ivailo Stoyanov 2007-10-08 10:33:28 PDT

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7

Comment 6 Ivailo Stoyanov 2007-10-08 10:45:43 PDT

Created attachment 313 [details]
The field in question isn't visible on my off-line copy of the page as well.

Comment 7 Ivailo Stoyanov 2007-10-09 00:51:03 PDT

Created attachment 314 [details]
The same page renders as expected in MSIE (6.0.2900.2180).

Comment 8 Ivailo Stoyanov 2007-10-09 01:29:10 PDT

Created attachment 315 [details]
... and also in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4

Comment 9 Ivailo Stoyanov 2007-10-09 03:29:09 PDT

After some research I have found that the form was blocked by an ad-blocking filter in my Firefox installation.

In order to prevent the "Supporting Agencies" form from being blocked I changed "sponsor" to "supporter" in the following fragment of the locally saved HTML copy.

            <table class="data" width="100%">
              <tbody>
                <tr valign="top">
                  <td class="label" width="20%"><label for=
                  "supporter">Agencies</label></td>

                  <td class="value" width="80%"><input class=
                  "textField" name="supporter[en_US]" id=
                  "supporter" value="" size="60" maxlength="255"
                  type="text" /></td>
                </tr>
              </tbody>
            </table>

Therefore I'd like to suggest this change to be implemented also in the HTML generating code in order to avoid such problems in the future (since most ad-blocking filters are naturally targeted at such strings).

Reclassified as "enhancement".

Comment 10 Alec Smecher 2007-10-09 16:39:14 PDT

Deferring for consideration -- I'm not sure we want to introduce confusion into the code just for one ad-blocking app. Thanks for tracking the cause down, Ivailo!