First foremost: I am aware that this is not a general Typo3 bug/error per se, as I have working installations. I am hoping for hints/help in finding the error in this installation, as it's way too big to just set it up as a new installation.
I have an erronous Typo3 10.4.17 installation (updated to 10.4.x, no fresh install)
Problem: Edited elements in workspace are not shown in the Frontend preview (opened via "Show webpage" or other basic means in BE) nor in the BE View-module.
Additional info #1: They are however shown when preview links are generated via "Generate page preview links" and those are viewed.
Additional info #2: Changed elements only become visible after publishing them & clearing Cache
Additional info #3: Clearing any Cache does not make them visible in the preview
After comparing all settings I could think of to another working installation I decided to delve into the core in search for a hint/solution and got stuck there at following point:
TYPO3\CMS\Workspaces\Controller\PreviewController
Line 130 $workspaceItemsArray = $this->workspaceService->selectVersionsInWorkspace()
As well as:
TYPO3\CMS\Workspaces\Service\WorkspaceService
Line 220 public function selectVersionsInWorkspace()
At this point my edited workspace version of the element does get retrieved. selectVersionsInWorkspace() does get called when viewing the preview.
While the PreviewController does not further filter the staged elements, they are not displayed in the Preview.
I am looking for any hint as to where selectVersionsInWorkspace() might still be filtered or other hints as to possible reasons/solutions for this problem that I may have overlooked.
Just when I decided to post to SO a co-worker found the reason...
As it's a big installation we use a dev-domain as admins and each website (over 100) have their own domains which are also set as base in the Site-config.
Only when the preview is opened as either the base or a baseVariant the workspace-elements are displayed at all. In older version the elements would still be displayed when opened via other associated domains, just sometimes not 100% accurately.
Letting this stay in case anyone ever has a similar problem and is hopefully able to find this.
Related
T3 8.7.15 with latest versions of tx_news and realurl. All was running just fine. Out of a sudden the following happens:
Click the link of a news article from a list view and it renders the detail view and displays everything correctly, as expected. When I then go back and click (any) another article it will again display the article I just view previously and will only display this article anymore, no matter which other I article I choose. It is always the first article rendered that is being displayed (until cache is emptied).
The links are correct according to the article chosen, by the way. However always the first viewed article is displayed, no matter what.
Have deactivated realurl but behavior is same. Clearing all caches did not help either.
Related to news and realurl there is a special page in the manual of news: RealURL configuration, the advanced configuration includes also some settings related to chache.
Additional you might have to adjust some general cache-setting.
Another point is that you've to clean the cache of realurl perhaps after having adjusted some settings.
Furthermore there have been some changes related to cache in core and viewhelpers too, I'm just not sure if they apply to news in general or to your individual new-templates:
Remove option cHashIncludePageId from cHash calculation
Make cHash configurable in Fluid Widget Links
Concerning this issue you've to verify your templates if they use any applying viewhelper.
If all hints never help to remove the undesired caching-behavior the simplest workaround is to disable the cache on the news-pages completely till a solution is found. I will update this answer if I find further information. Here is how to disable the page cache for a single page:
Open the page-settings of the page(s) where the news-plugin is resided
Navigate to the tab "Behavior"
Adjust the cache-settings
We have a site which sometimes delivers a wrong content for a specific URL.
The page has a plugin and by default should show the records listing (or the first record listing as the listing is grouped by initial letter). After clicking a link some records are viewable in detail on the same page.
Every now and then a cache problem occurs:
Instead of the listing a detailed record is shown.
Although we use realurl, all problems occur also with the basic urls.
For overview I will only write the url-parameters, assume www.domain.tld/index.php? in front.
The page to call is id=61.
What I see is
cHash=3df3421afc42d3d5bfa1bc50603ea00d&id=61&tx_citkoegovservicelight_ansprechpartner%5Baction%5D=show&tx_citkoegovservicelight_ansprechpartner%5Bansprechpartner%5D=282.
In the HTML-source of the page I show the page calling parameters with the extension page_params. Here I see:
tx_citkoegovservicelight_ansprechpartner[action]=show&tx_citkoegovservicelight_ansprechpartner[ansprechpartner]=282&tx_citkoegovservicelight_ansprechpartner[letter]=kontakt&id=61
Two strange notes: there is no cHash parameter, there is an additional parameter tx_citkoegovservicelight_ansprechpartner[letter] which never should be used with detail view and never should have the value kontakt (only single characters were used for the listing of all records starting with that letter = no detail view)
Using these parameters does not show the detail-view but the the list view (for letter 'A').
I do not find a reason why this special URL should be called (no link) and I don't know why TYPO3 should cache a content which belongs to another URL.
And it is a problem with TYPO3 cache as all works correct if I clear the cache of this single page.
Please check my answer to another issue. The accepted answer is right in that case, but in your case it can really be caused by failed cHash calculation, because it is not related to RealURL.
Try to clear the cache and then right after that go to tx_citkoegovservicelight_ansprechpartner[action]=show&tx_citkoegovservicelight_ansprechpartner[ansprechpartner]=282&tx_citkoegovservicelight_ansprechpartner[letter]=kontakt&id=61.
And then simply open the page id=61. If you see the wrong cached result, then the reason is in a combination of following factors:
Plugin's action is cached
Cache fails are allowed in installation
cHash calculation failed
To prevent this you should enable pageNotFoundOnCHashError in Install Tool. Then the problematic link above will just trigger 404 and will not force TYPO3 to render the page.
To a question where the link is coming from. If the website is already live, it can be everything: from a crawler, which somehow builded the link itself to a user who tried to play with parameters.
For the construction of an extensive list of links, since the source page is a thematic portal, I am looking for a suitable EXT., Which also runs under TYPO3 7.6 LTS.
it if the list of links to a permits the use of categories and multiple categorization of links is possible would be nice. should Weiterrhin the links are described not only the destination address and an alias but here should still an outline of the target page (possibly with photo) be possible.
Additional functions such as proposing links by users, reporting broken links or even a User Voting would nice additional features.
There were times the Modern Linklist, but they were no longer being developed for TYPO3 <6.x.
Is there perhaps somewhere an alternative or as one might like to vorhnandenen solutions might realize? It would be nice of course, without any programming knowledge, since I'm not a programmer.
P.S .: It is not about building a spam list but high quality links with topics relating to the original page.
As this seems to be a straight forward usage you could try to build that extension by yourself with the ExtensionBuilder.
just build up the records neccessary for your data. and let the EB generate all usefull actions: list & show, even create, edit, delete in FE would be possible.
Afterwards you just need to edit the generated fluid templates.
these links may help:
Overview
EB manual
small remark: if you want the newest code state, use the EB from git instead of TER
I`m not aware of an existing extension for it but it could be a good project to learn extbase / fluid.
You should also take a look at
typo3/sysext/fluid_styled_content/Resources/Private/Partials/Menu
and
typo3/sysext/fluid_styled_content/Classes/ViewHelpers/Menu
Fluid Content contains everything you need to create a list like that, you "just" have to combine the necessary bits and pieces.
You can do a lot with TYPO3 core functionality: there is a page type "external URL", pages can have categories by default, there are plenty of menu options (TypoScript HMENU, menu content elements, Fluid menu Viewhelpers). The Linkvalidator can periodically check all links and report broken links.
For suggestions you could add a form. Powermail for example can also store submitted info in database records, so your visitors could prepare page records (they are hidden until you make them visible).
I've a legacy app that features a DND from a popup window to the main one.
It works fine in IE 8 but not in any of the newer versions of IE. The effect results in the drag ghost image being stuck in the source window and not going away after the drop had occurred.
Some debugging did in fact confirm that the 'mouseup' event does not get propagated back to the source window. What can be done to fix it? Many thanks!
ITs a bit hard to begin to answer your question without some code....
use the File>Properties menu to find out which IE security zones the two windows(domains) map too...IE uses a different security model to other browsers... drag/drop is probably not allowed between local web files (using file: protocol) and internet or intranet sites.
Have you used the Dev tool yet to debug it? If you are using showModalDialog (which normally disables context menus) you can right click on a link (a) or input element to display the context menu so you can display the debugger for showModal content page.
If possible include a link to your website or a mashup (jsfiddle) with your questions.
I have installed SilverStripe on several servers successfully in the past (but I'm not a SilverStripe expert). This time my SS install fails to work and I'm at a loss how to fix it.
The Problem
SilverStripe 2.4.6 installed correctly on the server (AFAIK).
The front-end works as expected. (Show default theme. Pages all load correctly.)
I am able to log into the CMS admin section succesfully. The CMS loads but when changing site pages in the CMS using the browser pane on the left, the CMS shows the circular loading symbol. The new page load never completes.
Using the console of Firebug in Firefox - When attempting to change pages in the CMS (by clicking on the page browser pane) the CMS tries to load two pages. The second page request 404s.
The first GET request is from the initial page loads.
The following POST+GET requests fire when clicking on the page tree to change pages.
Attempting to Find the Solution
I've tried deleting and re-installing silverstripe twice. (2.4.7 and 2.4.6) Both times the problem recurs.
A strange thing is that this server is already running two other silverstripe sites (both of which I installed without a hitch). All three websites are accessed via different domains. I tried accessing this install via another domain thinking there might be something wrong with how this third domain is configured but that didn't help either.
What should I try now? I'm stumped.
Thanks in advance.
Responses to Comments
Check your root .htaccess file. Make sure RewriteBase is set to /
Checked. Full .htaccess on PasteBin
Indeed the javascrip URL is strange. Check if there is anything unusual about what's being returned from the previous POST request. Is the site running in dev, test or live mode?
I can't see anything unusual in the POST request.
Clue Found: The site is running in DEV mode. Switching to LIVE mode and the problem disappears. Also the second GET request only shows up in DEV mode.
Example Post request with response.
Example Get request with respones.
This is a work around more than a fix but if you'd rather be coding than bug hunting it might be worth a go! (remember to log out of SS before doing this fix)
In your mysite/_config.php file change
Director::set_environment_type("dev");
to
if(!isset($_GET['isDev']))
Director::set_environment_type("dev");
else
Director::set_environment_type("live");
Then you can develop the website in dev mode normally and to use the admin in live mode and avoid the bug you just go to: http://{your_domain}/admin?isDev=0
N.B. might find a proper answer when pastebin.com isn't overloaded and I can see your responses!