Updated 027 How to ensure that a field is not escaped when added to list views (markdown)

Amigo 2019-08-15 14:47:42 +02:00
parent 1947884bca
commit e45089ab26
1 changed files with 2 additions and 2 deletions

@ -18,13 +18,13 @@ In the Job Order Admin View area, in PHP, there is a method called 'Add PHP(geti
[00:00:58](https://www.youtube.com/watch?v=bfl0l3AoLKU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h00m58s)
Usually this would be added after the above was done, but in this case it was done before. [00:01:15](https://www.youtube.com/watch?v=bfl0l3AoLKU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m15s) A value is set up when 'danger' or 'warning' has to be applied by using the getDate and modifying it by the danger time and the warning time from the job tracking configuration values. This is a configuration field that has been added to the component. It's names are: 'warning time' and 'danger time' where the default is three weeks, one week. These are the dates that will be used.
Usually this would be added after the above was done, but in this case, it was done before. [00:01:15](https://www.youtube.com/watch?v=bfl0l3AoLKU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m15s) A value is set up when 'danger' or 'warning' has to be applied by using the getDate and modifying it by the danger time and the warning time from the job tracking configuration values. This is a configuration field that has been added to the component. Its names are: 'warning time' and 'danger time' where the default is three weeks, one week. These are the dates that will be used.
### Looping Through Data Till Target Found - Adding Styling
[00:01:44](https://www.youtube.com/watch?v=bfl0l3AoLKU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h01m44s)
Look through the data and identify data that is part of the target. Add this value to it, which in turn turns this red. (See video.) [00:02:19](https://www.youtube.com/watch?v=bfl0l3AoLKU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m19s) Check the dates and, depending on its values, add HTML value to the date. Use a custom method in a Helper Class called 'fancyDate', where the default sequel date is converted to a more appropriate date, 2nd of April etc. [00:02:39](https://www.youtube.com/watch?v=bfl0l3AoLKU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m39s) However, the problem is that if this is done and the component is compiled and items added , it escapes those values and prints it around the value. (See video.) [00:00:39](https://www.youtube.com/watchv=bfl0l3AoLKU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m59s) Obviously that is not the desired outcome. There is a way to prevent it. The value here is to create 'date' as well as the 'job status'.
Look through the data and identify data that is part of the target. Add this value to it, which in turn turns this red. (See video.) [00:02:19](https://www.youtube.com/watch?v=bfl0l3AoLKU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m19s) Check the dates and, depending on its values, add HTML value to the date. Use a custom method in a Helper Class called 'fancyDate', where the default sequel date is converted to a more appropriate date, 2nd of April, etc. [00:02:39](https://www.youtube.com/watch?v=bfl0l3AoLKU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m39s) However, the problem is that if this is done and the component is compiled and items added, it escapes those values and prints it around the value. (See video.) [00:00:39](https://www.youtube.com/watchv=bfl0l3AoLKU&list=PLQRGFI8XZ_wtGvPQZWBfDzzlERLQgpMRE&t=00h02m59s) Obviously that is not the desired outcome. There is a way to prevent it. The value here is to create 'date' as well as the 'job status'.
### Field Adding Escape=False To Code to Prevent Escape