You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you implement any of the ideas able, lots of users will be opening their pages in text view so that they can insert stuff. But all the code PLP adds makes this a very messy proposition.
For instance, PLP surrounds every line like this:
Three years ago
I imagine the code gets inserted when the “UPDATE” is clicked on. And there is probably no simple way to strip all that out on the way back. But it if there is a way to have this happen cleanly in the background right before the editor opens, that would be great.
The alternative would be to add a button that says:
Remove PLP Code
If the code was then stripped out but NOT sent back to the SQL table as if “UPDATE” had been pressed, the user would be presented with a much cleaner view of there code (in “text view”) making it easier to manually insert page breaks, etc., but no change will occur on the front-end yet.
Then, when the user finally decides to hit “UPDATE”, all the PLP code will get reinserted on the way back.
The text was updated successfully, but these errors were encountered:
If you implement any of the ideas able, lots of users will be opening their pages in text view so that they can insert stuff. But all the code PLP adds makes this a very messy proposition.
For instance, PLP surrounds every line like this:
Three years ago
I imagine the code gets inserted when the “UPDATE” is clicked on. And there is probably no simple way to strip all that out on the way back. But it if there is a way to have this happen cleanly in the background right before the editor opens, that would be great.
The alternative would be to add a button that says:
Remove PLP Code
If the code was then stripped out but NOT sent back to the SQL table as if “UPDATE” had been pressed, the user would be presented with a much cleaner view of there code (in “text view”) making it easier to manually insert page breaks, etc., but no change will occur on the front-end yet.
Then, when the user finally decides to hit “UPDATE”, all the PLP code will get reinserted on the way back.
The text was updated successfully, but these errors were encountered: