I installed TYPO3 ver 8.7.3 on my local machine using XAMPP. I want to build a website using Fluid Powered TYPO3, so I started to follow the instructions found in the documentation ( I'm new to this CMS ). I installed some extensions from the github page (https://github.com/FluidTYPO3) : vhs, flux, and builder. In the backend panel there is an icon under Admin Tools to access the Builder extension, yet when I click it there is an error :
Sorry, the requested view was not found.
The technical reason is: No template was found. View could not be resolved for action "index" in class "FluidTYPO3\Builder\Controller\BackendController".
I researched it thoroughly, and I couldn't find either the solution for this specific problem, nor anything that I could use to deduce anything helpful.
So, what should I do to resolve this ?
Related
I have a brand new TYPO3 10.4 install with a bootstrap sitepackage.
My page tree is this
Home
-> Building Management
--> Building Rules
Home shows fine, but all of the lower pages throw a 404 using the speaking url's, even from autogenerated links in the menus. I can still navigate using index.php?id=2, but this is not enabled at all by default.
If I set the language link to /en/ (rather than /) then no pages work, not even the home page.
I built the same site on my development server with the same version of typo3 and the same site package and it works as expected, just not on the production. Any idea where to look for a solution? Here's a pic of the site pagesites-page
The .htaccess was a clue. What appears to have happened is that the .htaccess file was not updated during the TYPO3 install. We copied one from another working install of 10.4.4 and that fixed it. I think there is a step in the install process that checks if there is a .htaccess file, and if there is then it doesn't copy or insert the required changes. Once we copied this across everything worked fine.
There was an error in the working CMS and I can not even enter management panel. I did not update PHP on the server, nothing changed in the configuration, and yet I can't enter the administration panel or display the WWW page.
When I try to get on administration panel or on website there is a message like this:
PHP Runtime Notice: Declaration of tx_ttnews_catmenu::wrapTitle() should be compatible with t3lib_treeView::wrapTitle($title, $row, $bank = 0) in /home2/izbampro/public_html/typo3/typo3conf/ext/tt_news/class.tx_ttnews_catmenu.php line 56
Is this a bug related to a too old version of PHP, or could someone break into the server and change the configuration?I have no idea what could have happened, everything worked well several days ago. Please help me with this error.
what do you mean with the administration panel?
in TYPO3 you have the BackEnd where you can do the normal administration and editorial tasks.
it is called normally with domain.tld/typo3/
the other area for administrative tasks is the Install Tool
which is called with domain.tld/typo3/install/
While the Backendneeds a running TYPO3 instance the InstallTool should be callable even if there is no configuration (e.g. database).
regarding your TYPO3 version:
we can guess a little bit with your data:
PHP 5.6.26 will let run TYPO3 only until version 7.6
the function reference t3lib_treeView::wrapTitle will restrict the version in the same way as the classname was available in core up to 4.7. for later version there existed an compatibility extension, first in core, later from TER.
if you have a look onto your server we might have further restrictions.
I will not exclude the usage of older versions up to 4.7:
these versions can be identified by files typo3conf/localconf.php, while since 6.0 the files are named typo3conf/LocalConfiguration.php.
In the same way there is a break in the storing which extensions are active in your installation:
up to 4.7 it was one line in typo3conf/localconf.php, since 6.0 it is an own file typo3conf/PackageStates.php.
You should be able to call the install tool, which will show the version (a screenshot from the appearance after the Install Tool login might help. But first we need to make you accessing the Install Tool.
Are you able to login to the install tool?
the TYPO3 version will decide about the next steps
I took over a website for my client and I tried adding an extension to Typo3. When I did, the whole website crashed and displays a HTTP ERROR 500. I found this thread with a similar problem, followed the instructions and erased the key that was supposed to be removed typo3 site offline after extension upload but that didn't work.
I gained access to the cPanel since I couldn't access the backend login page. So now i'm able to access all of the root files and hopefully fix the problem. Does anyone know anything to fix it?
You should read the error log (for the PHP service or Apache, depending on how your hosting works). There you can see the actual error message which then can give you an indication what's actually wrong.
The most common reasons are:
Extension version is not compatible with the version of TYPO3 you used (and you ignored the warning when installing).
Extension is written in a way that it assumes you update the database schema, which may not happen automatically when you install the extension.
Extension calls on classes that must be loaded and does not provide class loading for the installation you use (e.g. some extensions only offer composer support and won't work if you install without composer).
Extension uses PHP modules that are not installed or is incompatible with the version of PHP that is used.
You should be able to recover this by using the TYPO3 install tool to manually update the database schema and perform checks that the extension works (TYPO3 8.7+ only). If that does not help we will need additional information:
Which TYPO3 version do you use?
Was it installed with composer?
What is the exact error message you get in PHP error logs?
If the extension you installed is public, a link to it would help determine why you get the error.
Hope this helps!
I want to create VM theme in liferay 7. I made the changes in package.json and changed the templateLanguage to vm. Next I changed liferay-look-and-feel.xml and changed tag value to cm and did gulp build. The vm files are created, but when i Deploy it to the server, I get this warning:
09:53:24,368 WARN [Refresh Thread: Equinox Container: a046c07b-9d60-0017-134e-c4d1864b896c][ThemeHotDeployListener:129] Support of Velocity is deprecated. Update theme testTheme to use FreeMarker for forward compatibility.
Also in the browser, the control panel and header tabs are not displayed and instead a warning is displayed as below:
An app that can VIEW com.liferay.admin.kernel.util.PortalProductNavigationControlMenuApplicationType$ProductNavigationControlMenu belongs here. Please contact the portal administrator or install such an app from the Liferay Marketplace.
Below is the link of how the warning on browser is displayed: Image of Warning Message
What can be the issue?
I was facing the same problem when i migrated the application from 6.2 to 7. Liferay 7 supports freemarker template language. When I used Velocity i used to get blank page and page not used to get displayed. I advice you to use freemarker.
I'm having difficulty in integrating AEM 5.6.1 with Site Catalyst. It allows me to connect in the configuration successfully, but does not work on the framework setup.
I've followed the standard procedure to connect AEM to SC and it accepts my login in the configuration, but fails on the framework set up with the browser message 'We were not able to login to SiteCatalyst. Please check your credentials and try again.'. Behind the scenes in the server log;
12.12.2014 14:10:06.967 *WARN* [0:0:0:0:0:0:0:1 [1418393406764] POST /libs/cq/analytics/sitecatalyst/service.json HTTP/1.1] com.day.cq.analytics.sitecatalyst.impl.SitecatalystHttpClientImpl Data center 'https://api3.omniture.com/admin/1.3/rest/' responded with errors {"error":{"code":500,"message":"Internal Server Error"}}
12.12.2014 14:10:06.967 *ERROR* [0:0:0:0:0:0:0:1 [1418393406764] POST /libs/cq/analytics/sitecatalyst/service.json HTTP/1.1] com.day.cq.analytics.sitecatalyst.impl.servlets.SitecatalystServlet Call to SiteCatalyst method 'Company.GetReportSuites' failed com.day.cq.analytics.sitecatalyst.SitecatalystException: not authenticated
I've tried accessing via the API Explorer and it works.
I've tried the troubleshooting guide without success.
I can log in to Site Catalyst, I'm an admin, I am in the web services access group.
I've tried using a clean install of CQ5.6.1 with geometrixx - it doesn't work either.
I've tried this from a server and from a localhost/dev machine with the same results. No proxy. I've even tried using the shared secret as the password but then it doesn't connect at all, and fails on the configuration screen.
What might cause this to fail?
If it doesn't work with a fresh install and Geometrixx, then it's probably an Adobe bug. That's typically the first thing support will ask you about.
I would also verify using Geometrixx Outdoors, or a more recent demo site, on your fresh install, just to ensure it's not an outdated ClientLib issue.
I know this isn't a direct answer to your question, but honestly, I would approach the integration differently. I've worked with the AEM-SC framework and it's buggy at best. It's very finicky, it doesn't REALLY work the way the documentation claims, and it requires that you're very specific about what Clientlibs are on the page.
Moving forward, I think using Adobe Dynamic Tag Manager is the better approach, for many reasons. My understanding is that it's Adobe's recommendation as well. I'd consider moving to that. In AEM 5.6.1, you'll have to customize your integration with DTM, but it's not very hard.
Solution: Add a property on the configuration node for sitecatalyst: (eg. /etc/cloudservices/sitecatalyst/my-sc-configuration)
server=https://api.omniture.com/admin/1.2/rest/
it also seems to work with newer API versions such as https://api3.omniture.com/admin/1.3/rest/
It would appear that for 5.6.1 it ignores the OSGi configuration, at least for the configuration screens. With this extra property, the framework page loads without error and allows selection of the RSID.