• Home
  • Get help
  • Ask a question
Last post 11 hours 57 min ago
Posts last week 81
Average response time last week 4 hours 29 min
All time posts 67914
All time tickets 10497
All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.
Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!
All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#2650 – Problem with blog format

Posted in ‘sh404SEF’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Thursday, 25 August 2016 20:38 UTC
einternet
 Good afternoon,

We have a problem with all the url generated in the menu are the standard format joomla blog category.

Directly gives a 404 error and not find a way to fix it.

For example: https://xxxx.com/webinar/bigbluebutton/

Can you help please?
Friday, 26 August 2016 07:03 UTC
wb_weeblr
Hi

This 404 is generated by your server, not by Joomla (or sh404SEF). This means you have not enabled and configured URL rewriting on your server.

URL rewriting on your server is needed if you want to have URLs such as https://xxxx.com/webinar/bigbluebutton/

Without URL rewriting, URLs can only be similar to https://xxxx.com/index.php/webinar/bigbluebutton/

This is outlined in the Getting started guide: the first thing to do is to configure your server and Joomla:



sh404SEF extends Joomla! default SEF URLs system, so the first step is simply to enable Joomla! SEF URLs, and have them working properly before you attempt to switch sh404SEF on.



Enabling SEF URLs involves:



setting up your web server

activating SEF URLs in Joomla! configuration

selecting whether your server uses URL rewriting

This process is very well documented on this Joomla! documentation site page.


The link to the Joomla documentation page to help you configure your web server is: https://docs.joomla.org/Enabling_Search_Engine_Friendly_(SEF)_URLs

If you cannot configure your server properly, then you should set Jooma "Use URL rewriting" to "No". URLs will have "index.php" inserted in the middle, but at least they should work normally.

I would also suggest that during this phase, you disable sh404SEF (Enable URL optimization set to "No"). When you have Joomla SEF working, it will also work with sh404SEF, as there is no additional requirements on sh404SEF side.

Hope it helps

Rgds

 
Friday, 26 August 2016 08:56 UTC
einternet
Hello again,

The rest of the configuration and server joomla is correct, the problem is sh404sef, url work well all except those on the menu are blog format category.

After multiple tests, we have found that this only happens when we work with Nginx, with apache is working properly.

However our systems work with Nginx as the performance of Nginx against Apache is quite superior.

As we say, running Nginx, only it gives error with blog format category.

We would like to solve this, what can we do?
Friday, 26 August 2016 09:28 UTC
wb_weeblr
Hi

The rest of the configuration and server joomla is correct, the problem is sh404sef
Once again, this is NOT related to Joomla or sh404SEF.

At this moment, this page seems to work fine, so I cannot do a screenshot, but when I visited the first time, the error was a NGINX 404 error page. That means the request for that page does not reach Joomla.

As you are still running Nginx, and the page works fine, I think you probably found the source of the problem in the mean time.

Rgds
 
Friday, 26 August 2016 09:46 UTC
einternet
Hello again , the page is working well because right now is running Apache. Until we can fix this.

If switched to Nginx stops working.

Until a few days ago, we have been using AceSEF and worked properly , in fact if we cancel sh404sef and use the native joomla sef engine works properly, the problem only occurs with sh404sef running.
Friday, 26 August 2016 09:49 UTC
wb_weeblr
Hi

Hello again , the page is working well because right now is running Apache. Until we can fix this.
The page is running on Nginx and is working fine.

[xxxx]

I am confused, what's going in here?

Please get back to me when the page is NOT working and I can see it. Otherwise, we can't understand what's happening.

Rgds
 
Friday, 26 August 2016 10:01 UTC
einternet
Hello again,

The information is showing the browser is only the backend , that if nginx , despite the frontrend now is working with apache.

For you can see , we have once again changed the frontrend to nginx and back out again the error
Friday, 26 August 2016 10:05 UTC
wb_weeblr
HI

So you have a different web server for front end and backend? That's pretty unusual.

Anyway, I can see it again, and I can confirm, with a screenshot this is a nginx, web server issue:

[xxxx]

As you can see on the screenshot, this error is NOT generated by Joomla. The request is not even coming to Joomla (or sh404SEF). It's thrown directly by your webserver.

If you say that it works fine with only Joomla SEF, then I'm pretty sure it's an issue with the trailing slash.

Can you disable sh404SEF, and note what is the exact URL for this same page?

Rgds
 
Friday, 26 August 2016 10:12 UTC
einternet
Hello again,

Just off sh404sef , the url is different, but the same link in the menu without sh404sef the url is: https://xxxx.com/streaming-voz/webinar-conferencia-virtual-web-conference/bigbluebutton
Friday, 26 August 2016 10:16 UTC
wb_weeblr
Hi

Exactly what I guessed above: your nginx server is not configured properly: it doesn't recognize URLs with a trailing slash.

Just try try with that same URL with a trailing slash:

[xxxx]

You get the same 404 error from nginx:
[xxxx]

Rgds
 
Friday, 26 August 2016 11:09 UTC
einternet
Hello again,

We had not noticed that detail.

It was indeed a problem with the final slash.

If you are interested for other users, simplente must be added on the block configuration nginx the following line:

rewrite ^/(.*)/$ /$1 permanent;

For example:

server {
listen 80;
server_name www.mysite.com;
rewrite ^/(.*)/$ /$1 permanent;
}

Ty
Friday, 26 August 2016 11:15 UTC
wb_weeblr
Hi

Sorry, this is not a correct fix. What you are doing here is redirecting URLs with slash to the same URL without a slash. That's not good, and I don't event think it will work with sh404SEF, because with sh404SEF, the URL without a trailing slash does not exist and is a 404. Actually, sh404SEF will normally try to redirect /my-category to /my-category/, and then your nginx config will also try to redirect the other way around, resulting in an infinite loop.

The correct fix is simply to have nginx serve all URLs, with or without trailing slash. That's the most normal configuration, I'm not sure why this is not happening on your server, but that's where you have to look I think.

Maybe this can help you, here is a standard nginx config for handling Joomla URL rewriting

location / {
    
        index  index.html index.php;
        
        # serve static files that exist without running other rewrite tests
        if (-f $request_filename) {
            expires  30d;
            break;
        }

        # send all non-existing file or directory requests to index.php
        try_files $uri $uri/ /index.php?$args;
    }


Rgds
 
Friday, 26 August 2016 11:29 UTC
einternet
Thanks for the info

We have been able to fix the error
Friday, 26 August 2016 14:06 UTC
wb_weeblr
Hi

Glad you solved it. Closing this ticket now, feel free to open a new one as needed. If you do so, please mention this ticket number in the new one.

If you created any superadmin account for us, be sure to delete or block it now to avoid unnecessary risk in the future.

Be sure to also check out wbAMP, our new Accelerated Mobiles pages plugin for Joomla - the next big thing is SEO, direct from Google themselves!

Rgds
 
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.