Are you responsible for making OCS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.
Moderators: jmacgreg, michael, John
What to do if you have a technical problem with OCS:
1. Search the forum
. You can do this from the Advanced Search Page
or from our Google Custom Search
, which will search the entire PKP site. If you are encountering an error, we especially recommend
searching the forum for said error.
2. Check the FAQ
to see if your question or error has already been resolved. Please note that this FAQ is OJS-centric, but most issues are applicable to both platforms.
3. Post a question
, but please, only after trying the above two solutions. If it's a workflow or usability question you should probably post to the OCS Conference Support and Discussion
subforum; if you have a development question, try the OCS Development
In OCS 2.3.2,
The information in the notification emails that has been involved with TinyMCE in OCS backend (abstracts, signatures, ...) reaches target with html entities. However, if it is information that has been dipped in plain text, reaches target correctly.
There are many messages in the forum for this style, but I think the general issue would be it. Is there any simple solution to this?
- Posts: 285
- Joined: Thu Feb 07, 2008 3:35 am
- Location: Murcia, Spain
Just checking -- this is the same issue as viewtopic.php?f=2&t=6167&p=24219#p24219
, correct? Or is this a larger issue? In your previous screenshot (http://revistas.um.es/importpeerreviews.png
) it appears that some special characters are coming through fine (eg. "valor más alto"). I have already added the custom review form issue as a bug report, but I am happy to investigate other places where the same kind of problem happens.
- Posts: 4190
- Joined: Tue Feb 14, 2006 10:50 am
Return to OCS Technical Support
Who is online
Users browsing this forum: No registered users and 1 guest