My search results page images and URLs are leading to "localhost" instead of my domain (opulentjewelers.com) on my Magento2 install. The issue only exists on the instantsearch page -- the shop pages and Algolia autocomplete dropdown all lead to the correct URLs. Any idea why this issue is occurring? Thanks for your help.
In the Algolia, there are indexed URLs with localhost domain. In order to change it, you need to reindex your catalog from the production environment, not your local one.
If you use both environments and you're reindexing data from both of them, make sure you have set a different index prefix for each environment:
For example, on your local Magento instance you can have prefix magento_dev_ and in production you can use magento_prod_. Having different index prefixes makes sure that the extension won't target the same indices and therefore override your production data (titles, prices, URLs, images, ...) with development data.
Related
I would like to output additional data in most content elements (mostly fluid_styled_content) in the frontend for logged-in backend users (editing links for the CEs, additional information). The first idea was to insert additional Fluid code within <f:be.security.ifAuthenticated>. In theory this does the right thing, but the result is cached (bad: BE users might not see the additional data, others might see it). How does one work around this?
Ideas:
Use different templates for BE users. How?
Disable writing to and reading from the cache for BE users. How?
(Automatically) Assign a FE user group to BE users, because the cache should create different entries for each FE user group. How?
Render the additional output using JavaScript and get the data separately. Caching could work for all users, but complicated and would still require some way to discriminate between BE-/non-BE users. Would prefer not to implement this.
Requirements for a solution:
FE caching should continue to work for users which are not logged into the BE.
Caching for BE users does not necessarily have to work, but would be nice-to-have.
The output does not need to differ further between users.
You could deactivate the page cache for logged in backend users with a TypoScript condition:
[backend.user.isLoggedIn]
config.no_cache = 1
[global]
That seems excessive and there should be better solutions.
Ideas:
Add a cacheTag depending on BE login state (this would enable caching for all users)
disable caching in your content element definition's TypoScript by wrapping the FLUIDTEMPLATE in a COA_INT (see this SO post) (this would only disable caching for that FLUIDTEMPLATE)
Can <f:cache.disable> around the condition help? I found these to have no effect in plain content elements (FLUIDTEMPLATE), though.
Can <vhs:render.uncache> help?
I guess what you are looking for is called "frontend editing" - it is available as an extension that can be found here: https://extensions.typo3.org/extension/frontend_editing
Is there a possibility to update all slugs of all pages in all languages?
In an installation of one of my clients are hundreds of pages in multiple languages with wrong slugs (e.g.: prefix translate+german page name instead of translated page name etc.).
I remember an upgrade wizard in TYPO3 v9 but in version i cannot find this wizard.
This upgrade wizards appears if you just empty all slug fields of the table pages which is the fastest way to renew all slugs.
For special cases, maybe you would like to build your own Command.
Some nice thoughts (and helper methods) have been collected under TYPO3/Extbase How to create unique slug within create action?
i want to edit an existing Typo3 Backend configuration page.
I want to edit a configuration page like this here:
Where can i edit the extensions backend?
To be more clear: where can i change the edit page that an editor can use to change content.
Can someone give me a hint to the right directory or file in generall?
I'm using Typo3-7.6
Thanks
Sorry, can't manage to put all questions in an unformatted comment.
there are a lot of questions, as you are not clear what you want. Maybe that is a problem of the correct words, the vocabluary, but in TYPO3 we have some fix terms for specific object. And I think you do not handle these terms according to the TYPO3 community.
let's define some terms:
first the concept of TYPO3:
all data is stored in record of differnt database tables. All records are organized with some fields and teh main field is uid, the unique ID.
the main table is pages according to the folders of your disk. those folders can contain other records (like files). (nearly) each record in TYPO3 has a relation to a pagesrecord ina field named pid. even pagesrecords have this field and so they build a tree of pages and subpages.
There is one special page, which is no real page: the page with the ' uid' zero. As there is no real pagesrecord with the uidzero, there are other records with are stored in that page by having a pid zero. for example the start of your page tree is anchored in page zero, or global records like languages, user, storages.
Aside of being the anchor to other records, the pagesrecords have information themself. (page name, kind of page, a teaser image, SEO-information, visibility, accessibility, ...)
your screenshot looks like a content record (normaly in the table tt_content), in the lower right corner there you can see the table name and the uidthe the currently edited record.
'Backend': with backend we name the view to the data where an editor can change the content of the website. The real website is the frontend. This can be seen by everyone without the need to login in the backend (you might have access-restriccted areas of your website which need a login, but that still is 'frontend' as there is no option to edit content.
in the backend the editor might be restricted what he can access and what he can modify. An adminuser has no restriction (up until version 9 where the role of a maintainer occured to manage more general and basic options)
so we have not a single 'backend configuration page' but multiple places where we could configure special aspects of the website.
also there is no special 'extension backend'. we have global extension configuration and records belonging to an extension. (And an extension can enhance existing records with additional fields.)
Please be more specific what you want to change
I have a problem whose solution is certainly very simple, but it does not come to my mind at the moment :/
I have a multi-domain TYPO3 (6.1) installation and in one of the websites I need to temporarily show only one subpage, and over the rest of the pages I will work/update so I can not delete them. It is important that someone after entering a URL or going to the page from the Google search results has not opened this page, and has been redirected to this temporary.
I've tried the mount points but something does not work ...
Please help.
You can exchange the domain-records.
Make a new page on it's own (independent from the configuration of the domain it should replace). so it is a root-page. give it a domain record and disable the domain record of the pagetree it should replace.
Be aware to change the rootpageid configuration in realurl.
You also may need a special configuration for 404 handling for this domain as the most requests will be a 404 (or better 503).
And hurry up to update your system. TYPO3 6.1 is out of service for a long time.
I've done several sites with TYPO3 indexed_search. However I feel I still do not understand the nature of the relation between indexed_search and crawler. For instance, according to some authors to index tt_news I just need a generic crawler configuration and an indexed_search configuration for tt_news; but for other authors of tutorials and such I should create a crawler configuration for tt_news.
It is not clear to me what the relation is between crawler and indexed_search. How do they match? Shouldn't it be sufficient a root crawler configuration that when it finds an indexed_search configuration just runs it? Or does the URLs need to be generated by both? I've managed to create an index with just one crawler root configuration but I run the indexing through my own shell script that calls cli_dispatch.phpsh.
Are indexed_search and crawler redundant in terms of functionality (generation of URLs)?
Any clues are welcome.
Bests,
B.
Indexed_search can work without a crawler by indexing pages that are visited by visitors. The obvious disadvantage is that pages that aren't visited won't be indexed and thus won't show up in search results. If you have several frontend user groups configured then the chances that a page is visited are even lower.
The crawler can solve this by visiting each page. Furthermore it can visit pages as if it were member of (a combination of) FE user groups. This way it can help build the index of an entire website for all kinds of users.
Most of the details are explained in a tutorial by Xavier Perseguers. It's written for an older version but I guess that most of it is still valid.
(It's been a while since I last used indexed_search, but at that time the tutorial helped a lot).