interesting pageType issue for those who are interested:
I have a normal ajax call to a page with a pagetype number. On my dev machine, it works (osx with apache PHP 5.5), on my staging (linux / apache / php 5.5 )I get a pageType not configured error.
Now the funny part is:
the pagetype is 6732740021, but the error states it can not find a page with page type 2147483647.
Anyone has ever had this weird problem ?
Related
I have a plain naked TYPO3 8 lts installation.
But I cant login with the backend user.
Install Tool works fine
When I create a new BE user in install tool it does not work as well ...
any ideas?
Check in Localconfiguration the [BE][loginSecurityLevel] and change it to normal if it is rsa
For me the solution was deleting the cookies from the browser, then login form works good.
I ran to a problem where I couldn't login to backend, even if I had [BE][loginSecurityLevel] set to normal. Nether did it work on a unix system or windows. The reason I found out was, because the extension 'sv' was disabled (not in PackageStates.php array).
So I went to PackageStates.php and added following to the array:
'sv' => [
'packagePath' => 'typo3/sysext/sv/',
],
Before that happened, I downgraded TYPO3 from 9 to 8. I was able to log in first, but not the next day, after the first logout.
This extension contains core default services.
Use the Debugger for your browser, e.g. Firefox Developer, and check if an error is given there.
Loading failed for the <script> with source “http://www.my-typo3-website.de/typo3/sysext/core/Resources/Public/JavaScript/Contrib/jquery/jquery-3.2.1.js”.
If you copy and past the above url into a web browser, you will see this outpu:
The requested URL /typo3/sysext/core/Resources/Public/JavaScript/Contrib/jquery/jquery-3.js was not found on this server.
The file name jquery-3.2.1.js has been abbreviated into jquery-3.js!
It can happen that the jquery used by the login form is not included as needed. This can happend by a Rewrite rule in the .htaccess file which transforms the filename jquery-3.2.1.js into a smaller name jquery-3.js which will not be found, because it simply does not exist on the file system.
At least you should try out the original .htaccess file named "_.htaccess" which is shipped with TYPO3.
I updated PHP 5.6 to 7 and MySQL 5.5 to 5.7.
Everything was fine in the older versions, however since I updated the server some plugins such as: Custom 404 page, gregorian2jalali face problems. Some pages goes blank and the Inspect Element, Console section nothing shows. up. For example, if I activate gregorian2jalali plugin, User Profie page doesn't show up.
Also in the Custom 404 page plugin, the following error comes up in 404 pages:
A Question2Answer database query failed when generating this page. A full description of the failure is available in the web server's error log file.
There was a related question for an earlier problem here: When adding page link, database query error occurs.
In the Apache Error Log, a message similar to this message comes up:
PHP Question2Answer MySQL query error 1146: Table 'qa.qa_options' doesn't exist - Query: (SELECT 'options' AS selectkey, title, content FROM qa_options) UNION ALL (SELECT 'time', 'db_time', UNIX_TIMESTAMP(NOW()))
Also, there was an earlier problem here at this question: is there a way to manually create the database tables ?
Now that the plugin is not updated, how I can fix this problem ?
Thanks
Q2A version: 1.7.4
There are two possibilities I can think of:
You are using a different table prefix (e.g. abc_ instead of qa_) in your qa-config.php file, and a plugin is putting qa_options in their SQL queries instead of ^options as they should (which automatically adds the correct prefix).
Or, you are using the unstable 1.8 version from GitHub which currently has a few issues regarding plugins. If so, make sure you're using the stable 1.7.4 version that you get from the main Q2A site.
I have Bugzilla installed on Windows 7, Apache 2.4. It is accessible at: http://localhost:80/bugzilla/ which means when I type that address in my browser, I see the bugzilla homepage, I can login as admin and everything is fine.
I read in Bugzilla's documentation that Bugzilla has a "native REST API" that can be used to interact with it. For example it is alleged that sending a GET to the address: /rest/version will return the version of the installed bugzilla; The problem is, it doesn't!
I construct a request like: http://localhost:80/bugzilla/rest/version and I get a 404 not found error. I get this exact result for "any" request out of the rest documentation examples.
What am I missing? What am I doing wrong?
Incidentally, checksetup.pl shows that my installation is missing these 3 packages:
perl-ldap
mod_perl
Apache-SizeLimit
Could this be the cause?
Update 1: perl-ldap (Net::LDAP) installed. But cheksetup.pl still shows it as not installed and the problem still exists.
Update 2: LDAP installed but the problem still exists :(
My bugzilla installation also retuns "404 not found".
I had to use this URL to work ok: http://localhost:80/bugzilla/rest.cgi/version
Bugzilla installation comes with a default .htaccess file that does the rewrite work:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteOptions
inherit RewriteRule ^rest/(.*)$ rest.cgi/$1 [NE]
</IfModule>
All I had to do: "a2enmod rewrite" and "service apache2 restart" to enable the apache module, then the URL "website/rest/version" works ok.
I found a simple solution,
inside the rest API link you have to replace /rest/ to /rest.cgi/
example: The REST API for getting the details of bugs.
==> http:your bugzila ip/rest.cgi/bug (this rest.cgi syntax work perfectly)
I have created a simple hook for a Liferay site I have. It contains a 404.jsp that overrides the default Liferay 404. It works fine if I type in a specific page. For example:
Going to http://localhost:8080/jooky.jsp throws
SEVERE: PWC6117: File "C%3A%5Cbundles%5Cliferay-portal-6.1.0-ce-ga1%5Cglassfish-3.1.1%5Cdomains%5Cdomain1%5Capplications%5Cliferay-portal%5Cjooky.jsp" not found
in my Glassfish server log and redirects me to my custom /errors/404.jsp without a problem.
However, going to http://localhost:8080/jooky throws a different error
INFO: 14:07:41,790 INFO [PortalImpl:4873] Current URL /jooky generates exception: null
and redirects to a page within the portal that looks like this:
Can anyone help me redirect these non-file type URL's to my 404 page as well?
Thanks.
I was still struggling to figure out how to do this until I read the section in the Liferay Developer's Guide about "Overriding a JSP".
That told me exactly what I needed to know. Where the 404.jsp file should be stored in my hook, why there was a .portal.jsp file appearing in my liferay installation, etc.
One other critical thing that was not mentioned was the addition required to the portal-ext.properties file.
I had to add the following:
# 404 page
layout.show.http.status=true
layout.friendly.url.page.not.found=/errors/404.jsp
After a server restart, the 404 page started displaying for all incorrect pages.
I experience a problem with GWT 1.6 in IE8 (I have enabled native XMLHTTP support).
The scenario i this: The first time I enter a page, it renders fine with no problems. But in subsequent requests, the page fails with a JavaScript error:
Message: Exception thrown and not caught
Line: 5067
Char: 237
Code: 0
URI: http://someurl/somehashcode.cache.html
It happens in both standard mode and compatibility mode. The strange thing is that I do not experience the error when I run the application on localhost through the ASP.NET dev server. Only when I run it from a Windows 2003 server.
Does anyone have an idea, why this happens?
I would appreciate any kind of help - thanks in advance.
/Henrik
You always use the last version of stable release of GWT. This kind of error is from GWT compiler and you must report it to GWT team. Maybe this problem fixed in the last version of GWT.
I've seen the same issue, my feeling its coming from cached files. When the response is not from cached files I didn't see an exception.
I'm doing SSL to IE8. Microsoft have a fix you could try:
Internet Explorer file downloads over SSL do not work with the cache control headers
http://support.microsoft.com/kb/323308
Internet Explorer 7 and Internet Explorer 8
To resolve this issue in Internet Explorer 7 and in Internet Explorer 8, follow these steps:
1. Start Registry Editor.
2. For a per-user setting, locate the following registry key:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings
For a per-computer setting, locate the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings
3. On the Edit menu, click Add Value.
4. To override the directive for HTTPS connections, add the following registry value:
"BypassSSLNoCacheCheck"=Dword:00000001
To override the directive for HTTP connections, add the following registry value:
"BypassHTTPNoCacheCheck"=Dword:00000001
5. Quit Registry Editor.