These rules didn’t produce anything but a 500 error, when there were the only ones in, or had no effect at all, with the rest of the rules.
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-d
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} !-f
The image is not displayed, as you can see above, even though it’s there and has the same permissions as all other files and folders within plugins.
Is the mod_rewrite at play the problem?
How to fix this?
Thanks for noting that.
How do I set a variable to the baseUrl on a plugin tpl??
[UPDATE]
Never mind the last silly question…
Looked at other .tpl files…
{$baseUrl}…
duh…Felt quite a bit like Homer Simpson…
You’ll need to set a base_url[...] directive in config.inc.php, then likely use mod_rewrite on to get Apache to map the URL to the right place in OJS. This is a pretty typical mod_rewrite setup for OJS, so you can start with the configurations documented in this forum and elsewhere in the website.
Regards,
Alec Smecher
Public Knowledge Project Team
A 404 message (that’s not presented with OJS-style formatting) suggests that there’s a problem in your Apache configuration or your DNS setup. I’m not sure which it’ll be.
Regards,
Alec Smecher
Public Knowledge Project Team
ServerName revista.ibict.br
ServerAlias devojs
Alias /liinc /var/www/liinc (another journal that will be moved to the portal later on!!)
When pinging lalca.acv.ibict.br it points to a different server… Maybe that’s the issue? What should I tell the network support they should do?
I asked them to remove the DNS address altogether, but maybe that’s not enough??
These are all virtual servers.
The DNS sever pointed lalca.ibict.br to one virtual server.
Should it point to revista.ibict.br or the IP address?
Something else?
Here I go again with some mod_rewrite or redirect issues.
At ROAD registry, I’m not sure who did this or why, they have the wrong URL for our OJS installation: http://revista.ibict.br/ciinf/index.php/ciinf/index
I requested them to update it, but, while they don’t, how could I redirect this in a simple manner?
The general syntax of a RewriteRule is what pattern you want to match, followed by what you want that pattern re-written to, followed by any any flags. See the mod_rewrite documentation for details.
In your case, it might be as simple as rewriting that exact url to the correct landing page with a flag to use a redirect code of “301”.
ROAD has already fixed the info, but it’ll be available after their next update… I read the documentation a few times… sorry, but it’s cryptic writing to me… What I understand you’re telling me is that I could do this:
To get requests which come in on the wrong virtualhost off to your custom domain name, your mod_rewrite rule on the revista.ibict.br virtualhost for this journal should be something like: RewriteRule /lalca/(.*) http://lalca.acv.ibict.br/$1 [R=301]
This says, create a rule where anything requested under the “/lalca/” prefix is redirected to another “server” (virtual host really), and use a 301 (moved permanently) redirect.
You’ll then need a different virtualhost directive with normal mod_rewrite handlers.
Yes, probably the cleanest way to set this up is with Name-based Virtual Hosts enabled, with a VirtualHost for each logical grouping of DNS entries. Alternately, you will need some Rewrite Conditions which segment the requests based on the host name.