• Home
  • Get help
  • Ask a question
Last post 6 hours 58 min ago
Posts last week 247
Average response time last week 17 min
All time posts 56622
All time tickets 8814
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.

#8925 – Some errors with admin panel

Posted in ‘4SEO’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Sunday, 24 July 2022 16:24 UTC
christianrieger

Hi!

I got some problems in handling the admin panel.

1. Creating an error page fails

2. Creating analytics fails.

3. Redirects are not visible

Please see screenshots.

There's alwas the same list of errors like this one: Error: Invalid value for attribute width="1.25rem"

I tried with Safari and chrome on mac v 12.4

Please feel free to use the following admin access if needed.

www.xxxx.net

user: xxxx

PW: xxxx

Kind regards,

Christian

 
Monday, 25 July 2022 07:53 UTC
wb_weeblr

Hi

I can find only one error in the log file, and it's coming from MYSQL:

1 - What's the site hosting setup?

2 - Did this ever worked, or is the 4SEO installation new?

3 - Did you ran any prior version of 4SEO, like a beta version in the early stages?

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 

 

 
Monday, 25 July 2022 08:13 UTC
wb_weeblr

Hi,

Looking again at the error message, I can see this is due to the "list ordering" field in the database, so this tends to indicate there were a lot of rules stored at some point.

This makes me think again of an very early version of 4SEO which had a bug, creating a large number of rules (not visible from the UI). This was solved a year ago but maybe if you tried that version, you may still have that data stored.

As you don't seem to have done a lot of custom work in 4SEO right now, I would advise a full uninstall with data removal and then re-install. The data removal ensures that all database table are deleted, and then re-created afterwards. You will lose any data you have created, including all configuration in 4SEO.

If ok with you:

- go to Configuration | System

- scroll all the way down and enable "Remove all data when uninstalling" under "Data deletion"

- validate

- Uninstall 4SEO using the normal Joomla procedure

- download latest version and install again.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 

 
Monday, 25 July 2022 09:14 UTC
christianrieger

Ok I will follow your advice. But I can't find option „Data deletion". Is there a plugin to be activated?

 
Monday, 25 July 2022 09:16 UTC
wb_weeblr

Hi,

No, it's there:

- Configuration | System

- the last option on the page:

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
Monday, 25 July 2022 12:07 UTC
christianrieger

Hi

After the re-installation everything seems to work fine. Thank you very much for your fast support!

Best regards,

Christian

 
Monday, 25 July 2022 12:20 UTC
wb_weeblr

Hi

Glad it's sorted out! You did not answer about the site history: did you have 4SEO installed at any point in the past?

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
Monday, 25 July 2022 12:47 UTC
christianrieger

Hi

Sorry I forgot that.

I first installed 4SEO on Joomla 3 about three month ago after I bought a license. I remeber that analycing pages worked. After migration to Joomla 4 I did no further page analycing but I imported sh404sef meta data and redirects some times. And I rember the redirects have been visible with Joomla 4 with „(imported)" at the end. But last time I recognized them must be some weeks ago and I don't know with which version of 4SEO. Yesterday was the first time I tried the configuration of error pages and analytics with the actual version of 4SEO. And neither the default error pages nor the redirects have been visible.

In any case, I can rule out that I installed an early version of 4SEO a year ago.

Hope that helps.

Best regards,

Christian

 

 
Monday, 25 July 2022 14:14 UTC
wb_weeblr

Hi

OK, that's a bit odd because the bug that could have caused this was really in the early version, like the first 1.0.0 and maybe 1.0.1.

The other thing I can think of is if you had a large number of redirects imported from sh404SEF. Do you know roughly how many you had? a few dozens? a few hundreds?

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 

 
Monday, 25 July 2022 15:03 UTC
christianrieger

Hi

Yes, there are many redirects. You can check them at xxxx.info with the same admin access. This is the Joomla 3 installation from which I did the Joomla 4 migration. 4SEO shows 3516 redirects but I think there are less ( about 2500) because with listing 50 per page the last 12 pages from 71 pages are empty.

Back after content migration from k2 to joomla I tried a redirect rule for old k2 content/tag urls with sh404sef. But this never worked. You said there must be an extension causing an anwanted redirect. I never found out which one so I decided to create the redirects manually for k2 categories, items and tags.

The redirects are related to the urls of the actual still with k2 running live site xxxx.de.

Now I'm not shure if it's a good idea to import the redirects once again or if it's much more better to try a rule with 4SEO.

Best regards,

Christian

 
Monday, 25 July 2022 17:37 UTC
wb_weeblr

Hi

So yes, this is definitely the cause of the issue. There's a limit to the number of rules, but I did not think 2500 would hit that. I may need to change the type of mysql field for that data.

I need to revisit this. Obviously, rules are not meant to do that many one-to-one redirects.

Back after content migration from k2 to joomla I tried a redirect rule for old k2 content/tag urls with sh404sef. But this never worked

That's the ticket: https://weeblr.com/helpdesk/sh404sef/8405-301-redirect-alias-issue. The last message there was mine:

In my case, I actually tested: 

http://www.xxxx.info/abi-check-mathe-abi-skript-bayern/1-analysis/1-5-differentialrechnung/1-5-6-umkehrfunktion.html

You said this URL was not working but it is for me now, I'm redirected to 

http://www.xxxx.info/Abiturloesungen-Mathematik-Bayern/Mathematik-Abitur-Bayern-2013/Analysis-I/

Don't know what happened after that.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

which works fine.

 

 

 
Monday, 25 July 2022 18:32 UTC
christianrieger

Hi

Probably nobody but me will come up with the idea to create 2500 redirects in this way. I just couldn't do it any other way. And with copy and paste it didn't take that long.

The „working redirect" you mentioned leads to a completely different content.

/abi-check-mathe-abi-skript-bayern/1-analysis/1-5-differentialrechnung/1-5-6-umkehrfunktion.html

should be redirected to

/Abiturskript-Mathematik-Bayern/1-Analysis/1.5-Differentialrechnung/1-5-6-umkehrfunktion.html

And the redirect rule should be easy.

But anyway, I think I will try to create rules for those old k2 urls with 4SEO. Many of them are indexed by google.

So you can close the above sh404sef ticket.

Again, many thanks for your patiently support!

Best regards,

Christian

 

 

 
Tuesday, 26 July 2022 06:44 UTC
wb_weeblr

Hi

OK, yes, that'd be a better idea I think. Make to try and use the wildcard caracters and if not, come back to me, there's no reason this does not work.

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.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
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.