Last post 2 hours 33 min ago

Posts last week 141

Average response time last week 4 hours 42 min

All time posts 67805

All time tickets 10478

All time avg. posts per day 21

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.

#5870 – Help with Blog layout

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, 27 June 2019 10:35 UTC

builders

Hello

i have installed
Sh404sef: 4.16.1.3913
Joomla: 3.9.8

at joomla blog layout category i get the following error

The page isn’t redirecting properly

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

This problem can sometimes be caused by disabling or refusing to accept cookies.

I have tried everything can you please advise because the site is online ?

The url probelm is https://xxxx.gr/nea

Thanks

Thursday, 27 June 2019 10:46 UTC

wb_weeblr

at joomla blog layout category i get the following error

Is https://xxxx.gr/nea the full URL of the page with that problem? currently this URL is a 404.

Best regards

Thursday, 27 June 2019 11:06 UTC

builders

The non sef URL is
xxxx.gr/index.php?option=com_content&Itemid=123&id=21&lang=gr&layout=blog&view=category

From menu item the url i see is this
xxxx.gr/index.php?option=com_content&view=category&layout=blog&id=21

of course non is working

Thursday, 27 June 2019 11:12 UTC

wb_weeblr

Hi

1 - When I try to visit xxxx.gr/index.php?option=com_content&Itemid=123&id=21&lang=gr&layout=blog&view=category, I am redirected to https://xxxx.gr/blog/nea/

So I think you have enabled "301 redirect from non-sef to SEF". This is off by default and should stay set to NO. Also, make sure you also disabled (set to No) the option "301 redirect from Joomla SEF to sh404SEF".

2 - Have you made any redirect yourself related to that URL?

3 - Once you've removed the redirects, we can see what happens to that page.

Best regards

Thursday, 27 June 2019 11:23 UTC

builders

I have set those options to NO (it was at yes before) i also purged ULR's and no i have no custom redirects

We are closer to the solution ... now both non sef urls are working but if you hit the menu item is not working

Menu item URL
https://xxxx.gr/blog/nea/

Thursday, 27 June 2019 12:01 UTC

wb_weeblr

you hit the menu item is not working

1 - Is the URL blog/nea found in the SEF URL list?

2 - If not, what is the exact menu item type?

Best regards

Thursday, 27 June 2019 12:13 UTC

builders

1. Yes it is at SEF URL list .... it has also 2 Dulpicates

1 ad3 This is the main non-sef url! index.php?option=com_content&Itemid=123&id=21&lang=gr&layout=blog&view=category
2 adx Choose this non-sef url to be associated with blog/nea/ index.php?option=com_content&Itemid=177&id=21&lang=gr&layout=blog&view=category
3 a6w Choose this non-sef url to be associated with blog/nea/ index.php?option=com_content&Itemid=123&id=21&lang=gr&layout=blog&limit=24&limitstart=0&view=category

As i see the itemid=177 is my home page .... but the main that is the id 123 is the correct

2. The exact menu item type is Articles » Category Blog

Thursday, 27 June 2019 12:22 UTC

wb_weeblr

es it is at SEF URL list .... it has also 2 Dulpicates

Visiting xxxx.gr/index.php?option=com_content&Itemid=123&id=21&lang=gr&layout=blog&view=category now works normally.

As i see the itemid=177 is my home page .... but the main that is the id 123 is the correct

This is not about the content of the URL or anything related to menu items. What's happening here is a redirect: when someone tries to go to /blog/nea, the site responds by sending a redirect to the same URL, /blog/nea, instead of displaying the page content.

That redirect does not necessarily happens because of sh404SEF actually, it can be hardcoded in your .htaccess file or into any other SEO or redirect extension you may have.
Inside of sh404SEF, you should look:

- at the blog/nea record in the SEF URL list and see if there is anything listed under the Aliases tab
- go to the Aliases page and search for anything related to blog or nea

Best regards

Thursday, 27 June 2019 12:46 UTC

builders

If i close sh404sef is working... i do not use other redirect plugin (i only have joomla core enabled from global configuration)

The only extra code in htaccess is the 301 redirect from non www to www is that a problem ?

RewriteCond %{HTTP_HOST} ^xxxx.gr
RewriteRule (.*) http://www.xxxx.gr/$1 [R=301,L]

Do you want access ?

Thursday, 27 June 2019 12:47 UTC

wb_weeblr

If i close sh404sef is working... i do not use other redirect plugin (i only have joomla core enabled from global configuration)

WHich means the redirect was probably added in sh404SEF but not necessarily.

he only extra code in htaccess is the 301 redirect from non www to www is that a problem ?

No.

Do you want access ?

Yes, can be faster to get there.

Best regards

Thursday, 27 June 2019 13:00 UTC

builders

https://xxxx.gr/administrator/
xxxx
xxxx

Thursday, 27 June 2019 13:09 UTC

wb_weeblr

Hi

The account exists but it cannot access admin. It should be a superadmin account so we can access sh404SEF fully.

Best regards

Thursday, 27 June 2019 13:15 UTC

builders

Sorry

i now added Superadmin rights

Thursday, 27 June 2019 13:35 UTC

wb_weeblr

HI

Could not find anything related to this issue (there are a couple of things odd in the your setup but we can discuss that later). For now the next step is for us to take an akeeba backup of the site and restore on a local machine to be able to debug the code and find what exactly is doing this redirect, just for this URL. OK?

Best regards

Thursday, 27 June 2019 13:51 UTC

builders

OK

you can proccedd

Thursday, 27 June 2019 14:31 UTC

wb_weeblr

Hi

Well first result is that after taking a backup and restoring it as is on my local computer (took a while because the backup file is 1.13GB), including the .htaccess file, the problem does not occur. The page can be viewed with no problem.

This indicates the problem comes not from sh404SEF but from your hosting setup. Possible options are:

- a redirect set at your hosting company control panel level
- redirects rules at a CDN like cloudflare
- redirects set in your web server configuration file

Let me know.

Best regards

Monday, 01 July 2019 09:18 UTC

builders

Hello

i havetried with my server tech to find a solution... but no luck

we have no other redirect rules at conf file
we altered conf file of nginx but no luck
restarted the vps no luck ...
checked logs but found nothing

is there an other way to track down this error or to bypass it ??

Monday, 01 July 2019 10:23 UTC

wb_weeblr

Hi,

From our side, I can't think of anything else to do to be honest. Make a backup and installing locally is the ultimate thing. It takes a lot of time especially with large sites like yours but it's the ultimate tool: as we can setup breakpoints in the Joomla or extensions PHP code, we can track any issue to its root.

However this is tremendously difficult on a live server where cannot access the code with usual debugging tools.

One last thing that can be done is to check if the sh404SEF debugging feature yields some information:

- Go to the shLib system plugin and set all the Log messages settings to Yes
- Visit the "/blog/nea" page
- Set back all Log messages back to No
- Using FTP or CPanel, locate Joomla log folder (normally /logs). It will have an "sh404sef" folder
- Zip anything in the /logs/sh404sef folder and make it available to us either through FTP access or attaching the zip here if not too large

we altered conf file of nginx but no luck

What did you change exactly?

Best regards

Tuesday, 02 July 2019 14:19 UTC

builders

Hi

i have created the log file for sh404sef from joomla logs and i sent it in case you understand the problem ....

as i see there is a trailing slash missing and there is a loop of that redirect ....

Tuesday, 02 July 2019 14:20 UTC

builders

2019-07-02 14:12:35 128-debug - 115 ([email protected]) Starting to parse Joomla\CMS\Uri\Uri Object
(
[uri:protected] => https://www.xxxx.gr/blog/nea
[scheme:protected] => https
[host:protected] => www.xxxx.gr
[port:protected] =>
[user:protected] =>
[pass:protected] =>
[path:protected] => blog/nea
[query:protected] =>
[fragment:protected] =>
[vars:protected] => Array
(
)

)

2019-07-02 14:12:35 128-debug - 115 ([email protected]) Redirecting to correct url case : from https://www.xxxx.grblog/nea/ to https://www.xxxx.gr/blog/nea/
2019-07-02 14:12:35 128-debug - 115 ([email protected]) HomeLinks = Array
(
[el-GR] => index.php?option=com_content&Itemid=117&id=2&lang=gr&view=article
[de-DE] => index.php?option=com_content&Itemid=178&id=22&lang=de&layout=blog&view=category
)

2019-07-02 14:12:35 128-debug - 115 ([email protected]) Starting to parse Joomla\CMS\Uri\Uri Object
(
[uri:protected] => https://www.xxxx.gr/blog/nea
[scheme:protected] => https
[host:protected] => www.xxxx.gr
[port:protected] =>
[user:protected] =>
[pass:protected] =>
[path:protected] => blog/nea
[query:protected] =>
[fragment:protected] =>
[vars:protected] => Array
(
)

)

2019-07-02 14:12:35 128-debug - 115 ([email protected]) Redirecting to correct url case : from https://www.xxxx.grblog/nea/ to https://www.xxxx.gr/blog/nea/
2019-07-02 14:12:35 128-debug - 115 ([email protected]) HomeLinks = Array
(
[el-GR] => index.php?option=com_content&Itemid=117&id=2&lang=gr&view=article
[de-DE] => index.php?option=com_content&Itemid=178&id=22&lang=de&layout=blog&view=category
)

2019-07-02 14:12:35 128-debug - 115 ([email protected]) Starting to parse Joomla\CMS\Uri\Uri Object
(
[uri:protected] => https://www.xxxx.gr/blog/nea
[scheme:protected] => https
[host:protected] => www.xxxx.gr
[port:protected] =>
[user:protected] =>
[pass:protected] =>
[path:protected] => blog/nea
[query:protected] =>
[fragment:protected] =>
[vars:protected] => Array
(
)

)

2019-07-02 14:12:35 128-debug - 115 ([email protected]) Redirecting to correct url case : from https://www.xxxx.grblog/nea/ to https://www.xxxx.gr/blog/nea/
2019-07-02 14:12:36 128-debug - 115 ([email protected]) HomeLinks = Array
(
[el-GR] => index.php?option=com_content&Itemid=117&id=2&lang=gr&view=article
[de-DE] => index.php?option=com_content&Itemid=178&id=22&lang=de&layout=blog&view=category
)

2019-07-02 14:12:36 128-debug - 115 ([email protected]) Starting to parse Joomla\CMS\Uri\Uri Object
(
[uri:protected] => https://www.xxxx.gr/blog/nea
[scheme:protected] => https
[host:protected] => www.xxxx.gr
[port:protected] =>
[user:protected] =>
[pass:protected] =>
[path:protected] => blog/nea
[query:protected] =>
[fragment:protected] =>
[vars:protected] => Array
(
)

)

2019-07-02 14:12:36 128-debug - 115 ([email protected]) Redirecting to correct url case : from https://www.xxxx.grblog/nea/ to https://www.xxxx.gr/blog/nea/

Tuesday, 02 July 2019 14:26 UTC

wb_weeblr

Hi

OK thanks I get it now. Here is what's happening:

- the sh404SEF generated URLs is /blog/nea/ with a trailing slash. This is correct and exactly as it should be
- somewhere on your web server (or in another plugin but I tried to disable most of them) the trailing slash is removed.
- when the requests comes to Joomla/sh404SEF, it is now /blog/nea without a trailing slash
- seeing this, sh404SEF redirects /blog/nea to /blog/nea/. This is correct but because the web server is removing the trailing slash, it causes an infinite loop.

So the issue likely lies within the nginx configuration which does not account for trailing slashes in URLs. It's something I have seen before actually.

Here what we use:

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

This may not apply to your particular way of configuring nginx but it should help.

Best regards

Wednesday, 03 July 2019 08:55 UTC

builders

Hello

the problem solved we comment out a Joomla rewrite that removing slashes from nginx conf file

See the attached image

Wednesday, 03 July 2019 09:24 UTC

wb_weeblr

HI

Glad to hear that, I never think about custom web servers configuration as a possible cause for this kind of issues but I should!

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!

Best regards

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.