search

google-code-export / bignoze

Automatically exported from code.google.com/p/bignoze
0 stars 0 forks source link

Edit producer - store policy data migration #450

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
It appears store policies that have been migrated across into test retain any 
formatting it used to have - and the formatting cannot be changed in the Edit 
Producer page.

We may need to migrate the store policy across as plain text and then have the 
producers re-format.  But then we would lose all the formatting and may require 
a lot of work.

Additionally, we may need to add a few more functionalities back to the editor 
(e.g. font size, italics)

See attached.

Original issue reported on code.google.com by Miki...@gmail.com on 25 Jan 2013 at 12:31

Attachments:

GoogleCodeExporter commented 9 years ago 
Roy: Can we have your advice regarding this catch-22 data situation?

Original comment by Rob...@gmail.com on 25 Jan 2013 at 1:10

GoogleCodeExporter commented 9 years ago 
as a part of the requirement, we removed all formatting apart from the ones 
left there.

we did not migrate any data, they were there previously, we just removed some 
buttons from the editor as requested.

Original comment by Hui....@gmail.com on 25 Jan 2013 at 3:10

GoogleCodeExporter commented 9 years ago

Original comment by Rob...@gmail.com on 29 Jan 2013 at 1:59

GoogleCodeExporter commented 9 years ago 
Roy: as discussed today there are two actions:
(1) Include the "Remove formatting" option for the Store Policy on the Edit 
Producer page (merchant and admin views)
(2) I will see what level of html formatting is currently in the Store Policy 
field (using the Producer download) and investigate how easy it is to strip 
certain html tags.

Once (1) is complete please set to Ready for Test

Original comment by Rob...@gmail.com on 29 Jan 2013 at 6:39

GoogleCodeExporter commented 9 years ago 
We didn't have a clear formatting button previously
http://www.farmhousedirect.com.au/merchants/EditPolicy/patricenewellgarlic

But we dug up a button added it anyway

for more information - http://www.tinymce.com/wiki.php/Configuration:formats

Original comment by Hui....@gmail.com on 29 Jan 2013 at 7:41

GoogleCodeExporter commented 9 years ago 
Works for new text, but if I try on Myrtleford Butter Factory I can't clear the 
font sizes or the bolding (might be using an H tag)

Original comment by Miki...@gmail.com on 29 Jan 2013 at 9:39

GoogleCodeExporter commented 9 years ago 
please advise on the next steps.

this is the only button provided by tinymce

Original comment by Hui....@gmail.com on 29 Jan 2013 at 10:15

GoogleCodeExporter commented 9 years ago 
Rob, your thoughts?  If we get everything initially migrated in plain text, and 
still have this clear format option, it might still be useful.

Original comment by Miki...@gmail.com on 29 Jan 2013 at 10:23

GoogleCodeExporter commented 9 years ago 
Just a note: judging from View Source, the bold on the butter factory's store 
policy might not move because it's using "& g t ;" (without spaces) and "& l t 
;" instead of the "<" and ">" tags.

Original comment by Miki...@gmail.com on 29 Jan 2013 at 11:26

GoogleCodeExporter commented 9 years ago 
There are too many combinations in the store policy text formatting to run a 
script over them.  We will need to manually re-format the active-visible 
producers.  Hence on day one after go live the store policies will be poorly 
formatted but we can update then from that point.

In general the new clear formatting button on the Edit Producer page works and 
we can use that to clear the formatting and then use the bold and bullets 
formats, as required.

Where the clear forammting does nto work we must cut and paste the text from 
the Edit Producer page to a simple text editor - e.g. Notepad and then cut and 
paste it back (which will remove the formatting).

Original comment by Rob...@gmail.com on 4 Feb 2013 at 12:00

GoogleCodeExporter commented 9 years ago 
This is now part of the implmentation plan and will not be managed via the 
issue log.

Original comment by Rob...@gmail.com on 5 Feb 2013 at 10:34