An HTTP 304 response is not an error, but an expected response to a check for a page already cached in the browser.
Since OJS is apparently reporting success on saving the form data, you will want to next check your webserver error log for any non-fatal errors, such as problems writing to the cache files in your files_dir. Also try clearing your browser’s cache to confirm you aren’t holding on to any cached pages locally (though this is unlikely).
i had the same issue, i am using latest ojs version,
my php error is [06-Sep-2019 18:21:38 UTC] PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; CounterReport has a deprecated constructor in /plugins/reports/counter/classes/CounterReport.inc.php on line 33
The messages in your error log beginning with “PHP Strict Standards” or “PHP Deprecated” will not generally be helpful in diagnosing the problem. You are looking for messages in the error log at the time of the request that don’t contain these prefixes (look instead for “Error” or “Fatal” or perhaps “Warning”), or you may need to look in your web browser’s console for javascript error messages (in the case where the request never made it to the server).
Thank you
please find the errors
[10-Sep-2019 16:48:46 UTC] PHP Warning: Declaration of HypothesisPlugin::register($category, $path) should be compatible with LazyLoadPlugin::register($category, $path, $mainContextId = NULL) in /home/rubatosi/public_html/journals/plugins/generic/hypothesis/HypothesisPlugin.inc.php on line 67
[10-Sep-2019 16:48:46 UTC] PHP Warning: Declaration of PlagiarismPlugin::register($category, $path) should be compatible with LazyLoadPlugin::register($category, $path, $mainContextId = NULL) in /home/rubatosi/public_html/journals/plugins/generic/plagiarism/PlagiarismPlugin.inc.php on line 119
[10-Sep-2019 16:48:46 UTC] PHP Warning: Declaration of PlagiarismPlugin::getEnabled() should be compatible with LazyLoadPlugin::getEnabled($contextId = NULL) in /home/rubatosi/public_html/journals/plugins/generic/plagiarism/PlagiarismPlugin.inc.php on line 119
[10-Sep-2019 16:48:46 UTC] PHP Warning: Declaration of CoinsPlugin::register($category, $path) should be compatible with LazyLoadPlugin::register($category, $path, $mainContextId = NULL) in /home/rubatosi/public_html/journals/plugins/generic/coins/CoinsPlugin.inc.php on line 133
[10-Sep-2019 16:48:46 UTC] PHP Warning: Declaration of TexturePlugin::register($category, $path) should be compatible with LazyLoadPlugin::register($category, $path, $mainContextId = NULL) in /home/rubatosi/public_html/journals/plugins/generic/texture/TexturePlugin.inc.php on line 141
[10-Sep-2019 16:48:46 UTC] PHP Warning: Declaration of CustomBlockPlugin::getBlockContext() should be compatible with BlockPlugin::getBlockContext($contextId = NULL) in /home/rubatosi/public_html/journals/plugins/generic/customBlockManager/CustomBlockPlugin.inc.php on line 134
[10-Sep-2019 16:48:46 UTC] PHP Warning: Declaration of DRIVERDAO::setOAI(&$oai) should be compatible with PKPOAIDAO::setOAI($oai) in /home/rubatosi/public_html/journals/plugins/generic/driver/DRIVERDAO.inc.php on line 19
[10-Sep-2019 16:48:46 UTC] PHP Warning: Declaration of SwordImportExportPlugin::register($category, $path) should be compatible with Plugin::register($category, $path, $mainContextId = NULL) in /home/rubatosi/public_html/journals/plugins/generic/sword/SwordImportExportPlugin.inc.php on line 233
[10-Sep-2019 16:48:46 UTC] PHP Warning: Declaration of JournalOAI::sets($offset, $limit, &$total) should be compatible with OAI::sets($offset, &$total) in /home/rubatosi/public_html/journals/classes/oai/ojs/JournalOAI.inc.php on line 230
These warnings are also only relevant to developers, and won’t have a practical effect. If this issue aligns with the earlier report (where the cache file was not writable), look for messages at the time of trying to save the settings where there is a PHP Fatal or PHP Error, or a PHP Warning that relates to file permissions.
If there are not messages like that, look for any javascript error messages in your web browser’s console (described above with the keyword of “Web Inspector”).
Thank you
here was what i find in console while saving
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help http://xhr.spec.whatwg.org/ jquery.min.js:2:79419
The resource at “” was blocked because content blocking is enabled. 2
The resource at “https://media.licdn.com/dms/image/C5103AQGHJq5iC0GDSA/profil…0988800&v=beta&t=qYXNj0DE4DjZIcpicP0D0cNprRwGT3Xb3sGKqaIs5dc” was blocked because content blocking is enabled.
The resource at “https://media.licdn.com/dms/image/C5103AQGHJq5iC0GDSA/profil…0988800&v=beta&t=qYXNj0DE4DjZIcpicP0D0cNprRwGT3Xb3sGKqaIs5dc” was blocked because content blocking is enabled.
MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. 2 tinymce.min.js:2:9014
None of these seem link something that would prevent data from saving in the Masthead, though the message of “The resource at “” was blocked because content blocking is enabled” is odd.
If you open the Network tab before you click Save, then click Save so the new traffic is caught, can you screenshot the results? It should look something like this.
Hi, Please find the attachment of screenshot
The 403 error indicates the request is not making it to OJS:
how can i resolve it
You will need to identify what is generating the 403 response. If your webserver is generating the 403, you will see an access log line with the request and response and probably an error log line with more details; if something before your webserver (like a proxy or firewall) is generating the 403, you will not see an access log line, or a error log line on the webserver.
You’ll want to check with your system administrator or hosting provider for additional suggestions. It seems like this message is coming from a component before OJS gets the request.
hi got this error messgae from administrator " ModSecurity: Warning. detected XSS using libinjection. [file “/etc/apache2/conf.d/modsec_vendor_configs/OWASP3/rules/REQUEST-941-APPLICATION-ATTACK-XSS.conf”] [line “37”] [id “941100”] [rev “2”] [msg “XSS Attack Detected via libinjection”]"
I suspect this is a false positive match, but can you request the logdata associated with this event? Is should be of the form:
Matched Data: %{TX.0} found within %{MATCHED_VAR_NAME}: %{MATCHED_VAR}