Archive-path doesn’t work under ojs 3.1.2.1 - ojs

Since the update of OJS to 3.1.2.1, OJS, if I want to reach the archive, throws an HTTP code 500 that the request could not be processed. There is nothing in the errorlog about this call, so I have no idea where this error occurs.
Now my question is whether this problem is already known and if so how I solve it.

The problem was the bootstrap3 plugin which was still running on an old version, an update to the new version solved the problem.

Related

Guidewire PolicyCenter The object you are trying to update was changed by another user. Please try your change again

I'm having this weard mistake "The object you are trying to update was changed by another user. Please try your change again." I would like to know what is the reason of this without context. There are no logs about it, no exception stacktrace, no information about this mistake in documentation. I believe this is something about Bundles but I want to now the exact reason
GW throws several exceptions related, by example ConcurrentDataChangeException, DBVersionConflictException depending of entity type. It occurs when a bean is modified concurrent by two or more transactions (bundle).
This error usually happens because on one bundle two transaction changes are trying to commit where prior bundle is still not committed.
Let us understand with one example- There is user which does a policy change to add any contact or any other business operation. And at the same time another user open same transaction in his GW PC UI and tries to do some business operation at this GW system throws this error on UI because the pervious bundle is still not committed.
The error trace leads you to some OOTB java classed and I think you can get it from PCLogs from PC UI Server logs.
Hopes this clarifies you.
Actually this happens because your object was updated by someone else on the DB during your db read from the DB and your attempt to write it back into the DB.
GW does this by leveraging the version check from your database object.
The exception message actually tells you who and when did the conflicting update. There're no stack traces that will point you to the cause of the other update.
Root causes might be several - from distributed cache in clustered env going out of sync to actually having some other party doing work on the same entities as you do. So the fix is per case really.

XPages OpenLog - Logging to wrong database

Apologies Paul, this is a duplicate to the post I put on OpenNTF, however the site will not allow me to log in the last 2 days to follow up, plus the wider audience of Stack might find me someone with an identical issue.
To keep it short.
I have 1 openLog database in a folder structure, logs/xpageslog.nsf
During development, I could log to this database, for example, using Paul Withers XPages OpenLog Logger, to log uncaught exceptions with the following settings:
private String logDbName = "logs\\xpageslog.nsf"; // in OpenLogItem.java from OpenLogClass library
logDbName = "logs/xpages.nsf" // in OpenLogFunctions.ls
xsp.openlog.filepath=log/xpageslog.nsf // in xsp.properties
However, if I then change all the above, to simply go to xpageslog.nsf, in the root of the server (this is a 2nd openLog database) errors still get logged to the first database.
I've tried building, cleaning, re-compiling, all to no avail. It seem's to be that somewhere, or somehow, the references to the original database are not being overwritten.
Any ideas?
It is good practice to use restart task http instead of tell http restart. Both commands have different effects.
As confirmed in comments, this solved the problem.
Some use tell http quit followed by load http, the effect is the same as with restart task http. At the other hand, simple tell http restart does not fully initialize http task, it's kind of soft reset and I recommend not using it.

Meteor iron:router - weird no routes defined

I have a meteor 1.5 application which had no problems last night, everything worked just fine, all routes defined by iron:router were working. Today, out of nowhere and without changing any code, i have this weird error page of iron:router saying that i have no routes defined.
I have done some research and found out that the latest version of iron:router have some conflicts and it causes problems, some suggested that i downgrade iron:router, i have done that but it didn't work.
i even tried removing all my routes and putting one simple route for the homepage with url " / " but still get the same error page
Any ideas ?
This message was also encountered by users when Chrome moved from version 50 to 51. Have you tried different browsers to see if the issue is specific to a certain vendor? (git topic)
Rgs, Paul

error 500 http web server: command not handled exception

I think this topic a lot of ppl post it already. I also look for lot of thread in stack overflow and some ibm page. They do give some comment of how to solve this problem. But i still facing the same problem, it still give this error.
Case start :
Actually one of my customer, they have facing this error during running on webpages and also notes ~
error 500 http web server: command not handled exception
Action taken but not solve:
The user id signing/creating the XPages allowed to run XPages in the
server document?
Do project clean, build automatically on designer
Do testing on creating new xpages page with simple lable " hello world" , this one can run successfully only.
Try to reload the http server by
tell http quit
load http
After do this the problem still same give the same error. May i know got any other way to solve it?
"Unresolved compilation errors: java.lang.String" points to a failed install as here. A class in java.lang or java.util should always be resolved. Ensure all services and any processes for Notes / Domino are stopped before the relevant install, jar files can get locked once used. Xpages can't load, Error 500; java.util cannot be resolved
Switch on "Display XPage runtime error page" in application's XSP Properties then you'll see a detailed error message which probably will lead you to the issue:
I frequently get this error when there is a mismatch/problem with access rights or the user login has expired and the app/database doesn't redirect to the login page. I suggest you double check the security basics first. (Might also explain why the app works locally, but not on the server).

What does it means &sa=U&ei?

I have a website, today looking at the log, I found some request to a page from my server with appended this variable &sa=U&ei.
Could you tell me guys what &sa=U&e could mean? Could be an attempt to find Nullable Scrips? Could be a security threat?
&sa=U&ei=XuRBT92UFseYhQf_w7HeBQ&ved=0CNYBEBYwYw&sig2=Rt1Cr_FCPD1-6VYu__Oavg&usg=AFQjCNFlHVaDQL--kgDbOn2vNgUqwUOsTA
The error in my log is:
A potentially dangerous Request.Path value was detected from the client (&)
http://www.bleepingcomputer.com/forums/topic442637.html
But nevermind. I found the offending culprit. Seems that for some
reason my "GoogleEnhancer" became "incompatible" with Firefox. It
worked fine even before I updated to 10, but go figure. And it wasn't
the whole add-on, it was the "Use Google Classic" radio button turned
on. I got this add-on after Google started making their search engine
so... oh, what's the word I'm looking for... umm... oh, yeah...
crappy!
http://www.ausforces.com/showthread.php?6595-Google-is-acting-odd...
I figured out what it is... I have an add-on called google enhancer
which obviously hasn't been updated properly of late. Disabled it and
it worked fine. Well that was a waste of a thread. Thanks for the help
though guys.
So, the unnecessary part of the request is created by an outdated add-on for Firefox, nothing serious. The visitors with that add-on have more problems than your website :)
Practically, it could just be simple url request.
And the random texts you are seeing could be an autogenerated random string to maintain sessions. As there seems nothing wrong with the URL, and those sa and ei simply means, that these get variables are assigned some values, which would then be used in your application, for may be session management or other purpose.
From the face of it, it doesn't appears to be any hackable stuff.

Resources