Last post 57 min ago

Posts last week 94

Average response time last week 34 min

All time posts 67886

All time tickets 10493

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.

#4522 – Eport metas, purge SEF URLs, import metas, records not shown in the Joomla administrator consoles.

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.

Wednesday, 17 January 2018 23:14 UTC

Dear support,

I have a totally new website build from the stretch with the latest software versions brand new installed.

I started yesterday to use your "Title and metas" function (for the first in my life). After doing that I wanted to let your sh404sef rebuild all the SEF URL's as I did some big category changes, which I want to get reflected in my SEF URLs. So I exported my 103 lines "Title and metas", see attached file.

Then I purged all the 800+ records from the "SEF URLs" view. After that, I imported the file attached with the import button in the "Title and metas" view of your software. The message was that all the 103 lines were imported correctly. However, they don't show up in your "Title and metas' view and also not in JSitemap Pro - SEO spider. So I looked with phpMyAdmin, in the database table #__sh404sef_metas. I was happy to see that the 103 lines look fine and complete there.

Do you have any idea, why these imported database records don't show up after the (successful) import in the sh404sef and the JSitemap PRO Joomla administrator software? What is your advice to get this fixed?

With thanks in advance, Nico

P.s. cannot upload the file in your support tool, but can mail him to you on request.

Thursday, 18 January 2018 10:59 UTC

wb_weeblr

Hi

1 - If the data is in the database, then the file import worked fine. The process you used was fine.

2 - What JSitemap sees is not relevant and a good test. The only valid test is to select one single URL with custom meta data, load it into your browser then open the source code view (CTRL+U for most browsers) and look at the actual content, specifically the page title and meta description for instance. Any other testing method is not reliable. Once you've checked afe w pages you can then run a crawler to automatically check a large number of pages.

3 - The title and meta data in general is attached to the non-sef URL of a page (ie the real, internal URL). What could have happened is the following:

You had a URL such as index.php?option=com_content&view=article&id=12&Itemid=34&catid=56, and you attached a custom page title to that.

Then you moved that article from category 56 to category 78. This means Joomla now creates a URL for that page as:

index.php?option=com_content&view=article&id=12&Itemid=34&catid=78

and therefore the custom meta data is not found.

I would suggest:

1 - Check if this is what happens here: compare the non-sef URL for one single record in the #__sh404sef_metas table to the non-sef URL displayed in the URL manager for that page.

2 - Also, just in case, see that if you now set a custom page title or description for a page, with the new SEF URLs, you indeed actually get that title/desc in the page source code.

Depending on the answer to both those questions, we can then advise next steps.

Rgds

Thursday, 18 January 2018 12:46 UTC

Hi Rgds ;-)

Thanks, I think you have helped me a lot with your scenario above and I think we are almost there.

In conclusion: When I input new meta data in your sh404sef component, it is back on my pages and then there is a new record added in the database. Almost the same but now with ...&lang=en.... while the old import record has ...&lang=nl....

nl is my lang, and it should not been set to en. When I look at my eport file it is all set to en so the import didn't change that. So I think that the export function doesn't support nl language setting and has changed the non-sef URL lang to en? Importing a file just exported in the same system without any other system changes (only purge 800+ records within the sh404sef component from the "SEF URLs") should work without lang setting changed. Where can this has been going wrong?

With kind regards,
Nico

Thursday, 18 January 2018 12:54 UTC

wb_weeblr

Hi

Not sure I understand, this:

In conclusion: When I input new meta data in your sh404sef component, it is back on my pages and then there is a new record added in the database. Almost the same but now with ...&lang=en.... while the old import record has ...&lang=nl....

and this

When I look at my eport file it is all set to en

Seems to contradict each other.

Can we clarify:

1 - the non-sef URLs in the exported file have all &lang=en instead of &lang=nl?
2 - When you now create a new meta data for a given URL, is it stored with en or nl?
3 - Is your site set to NL for both front end and backend, or just the front end?

Rgds

Thursday, 18 January 2018 13:27 UTC

Hi,

Yes sorry, my lang in dutch/nl, so English is difficult for me.

1 - the non-sef URLs in the exported file have all &lang=en instead of &lang=nl?
----->YES
2 - When you now create a new meta data for a given URL, is it stored with en or nl?
-----> nl
3 - Is your site set to NL for both front end and backend, or just the front end?
-----> I thought everything was set to nl as I had installed nl packet and marked Dutch (nl-NL) as default language in Administrator: Extensions - Langueage(s). Now, after your question, I was looking for another language setting and saw there is also a second menu item "content language". I guess that is what you ment with front-end language? There Dutch (nl-NL) was still unpublished, so I have published it and unpublished English (en-EN) there. Will that make sense and solve the case for the next time?

Regards, Nico

Thursday, 18 January 2018 13:42 UTC

wb_weeblr

marked Dutch (nl-NL) as default language in Administrator: Extensions - Langueage(s)

When you do that, you basically have to do it twice: once for the "Site" and once for the "Administrator" side:

I was thinking that the "Administrator" was maybe still in English? Likely not, but still possible.

? There Dutch (nl-NL) was still unpublished, so I have published it and unpublished English (en-EN) there. Will that make sense and solve the case for the next time?

Yes, most likely.

Rgds

Thursday, 18 January 2018 13:54 UTC

Thanks for all you quick and good support !!!

Oeps, I didn't see that drop-down :-(. You are right, "Administrator" was still in English, I have now changed it to nl. Sorry :-(

I guess case solved now and you can close this ticket. I will just change the "en" to "nl" with phpMyAdmin directly in de database and after that I think sh404sef will reload it and activate it in your component.

Many thanks,
Nico

Thursday, 18 January 2018 18:11 UTC

wb_weeblr

I will just change the "en" to "nl" with phpMyAdmin directly

Yes that sounds like the way to go. Be sure to test first with one single URL and see that you get your meta data back.

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.