I'm a new beginner to Joomla. I'm trying to build a website with a sub domain of joomla (free sub domain). After successfully setting up and installing the database plus other components according to several beginners' tutorials, where I successfully upload several templates, I try to test the link of my website but all I get is this error message:
The requested page can't be found.
An error has occurred while processing your request.
You may not be able to visit this page because of:
an out-of-date bookmark/favourite
a mistyped address
a search engine that has an out-of-date listing for this site
you have no access to this page
Search
You may wish to search the site or visit the home page.
Search ...
Search ...
Home Page
If difficulties persist, please contact the System Administrator of this site and report the error below.
404 Article not found
How can I really go about solving this issue because after intensive research I have found out that this error message is very common for beginners when it comes to Joomla.
Some Suggestions:
SEF URLS
Try using a non-SEF URL to access an article to see if that works.
For example, check in Content -> Articles for a valid published article ID (the article IDs are in the last column at the right hand side of the page) and access the page using a URL like this:
http://[your-domain-name].com/index.php?option=com_content&view=article&id=xx
where xx is the article ID.
If this works, then your problem has something to do with SEF URLs or URL Rewriting.
You can temporarily disable SEF URLs and URL Rewriting in the Global Configuration.
.htaccess
A badly configured .htaccess file could cause this issue.
Assuming the .htaccess file exists in the root folder of your website (e.g. in the /public_html folder) then try copying .htaccess to .htaccess.old as a backup and reset the .htaccess file to the default settings by copying htaccess.txt to .htaccess.
htaccess.txt should also be found in the root folder of your website as part of a normal Joomla install.
Test whether this fixes the issue.
Third Party Extensions
Try disabling any SEF related third party extensions.
Related
I have a strange problem with Magento Connect Manager: firstly, if I cliick the "settings" tab, the page redirects to an the 1and1.com.com homepage with an affiliate link suffix (1and1 arent my hosting provider).
Similarly, if I try and uninstall / reinstall any extension on the "extensions" page, the same 1and1.com page appears in the window below the list of extensions (where you would normally see the installation being actioned).
I am also unable to install any new extensions / or uninstall any existing ones. I'm guessing this is the result of some malicious code being inserted somewhere?
does anyone else have any similar experience or any idea how to fix?
Thanks in advance.
Rollback your updated htaccess to default magento htaccess and clear your cache and test again.
OR
In your current htaccess file you may find some urls like
http://www.yourdomain.com/
update them to your website url.
I have to do some modifications online on my website, and I don't want the users to see those pages. So I renamed index.php to index_orig.php and I put another index.html that show a message (WebSite under construction) for my users.
My problem is that I want to access online to the rest of my pages to check the modifications until satisfaction, but when I try to access the rest of the pages by their whole URL (404 error is shown).
Example : www.mywebsite.com/floder1/pagetarget.php.
Put back index.php.
In your global configuration, set the site to offline and put up a message and a logo etc (assuming you are on 2.5 or 3). You'll be able to login and see the site.
Please keep in mind that in a database driven cms there are not pages in the way that you would think of them in a static html site. Everything gets pushed into the index.php of your template file.
Update the directory default document on whatever webserver you are using. Also update any rewrite rules that may be pointing to index.php
I have a magento site running locally using WAMP and it works great. However I need to create a different site so I created a folder for this new site under htdocs.
In that folder I loaded the Magento files.
Created a new database for newsite with all rights in phpmyadmin.
Went to the localhost:8888/newsite and started Magento installation wizard.
In the configuration section of the wizard I entered all the info required: db name, user, password. For URL Base I used the default (http://localhost:8888/newsite). Selected allow charts and Allow apache rewrites. Finished installing magento.
Now magento is running on newsite. I can see the front and back-end of the site.
Here is the problem: When I create a category and/or subcategory, magento does create the menu link but when I click any category, the browser takes me to a 404 not found. Upon analyzing the URL that took me there i see that the URL is : http://localhost:8888/newsite/category.html BUT by adding "index.php" into the URL (http://localhost:8888/newsite/index.php/category.html , the page does work!
So this means magento IS creating the page for the category but the linking is somewhat wrong.
Now, I've been making sure that rewrite is enabled and after all, the other site I mentioned I have is working properly, so I assume rewrite is properly enabled.
So I need help finding:
Why is one site working and the other isn't?
How can I fix this issue?
Thank you!
Sounds like you haven't copied over the .htaccess file (in your Magento root folder). You need this file for the Apache rewrites to work.
I've just moved a Joomla 1.7 site to a new server.
Administration back-end works fine. Configuration.php seems fine. Get "The requested document was not found on this server." for every page other than Home.
Must be talking to the database OK or I'd get an error. Could this be a problem with the PHP?
Thanks,
Andy
Did you clear joomla cache ?
Disable page and/or module caching.
Disable any plugin that optimizes "loading speed".
Try removing SEF URLs (Joomla! and any 3rd party extension).
If you are using a custom .htacess, then use an unmodified joomla one.
Disable some system plugins.
Disable modules in the homepage.
Have you tried using another template (site) ?
You have Seach Engine Friendly URLs enabled in /administrator/ area's global configuration settings. You have probably enabled the option to use the mod_rewrite function which removes the /index.php/ portion of the urls.
It is a requirement of this mode that you have the .htaccess file in place in the root of your site. You probably had this correctly configured on your development server but perhaps forgot to move the file across when you went live. Some FTP programs hide dot files (files starting with a leading dot in the filename) so depending upon how you transferred the files (I'm guessing manually with FTP rather than Akeeba backup or similar) the file may have been missed. Look through your FTP client's options/preferences for an option to show/hide hidden files.
Failing this - the file could be correctly in place - but if you were developing in a sub-folder on your development server you would have set the RewriteBase line to your /sub-folder/
RewriteBase /sub-folder/
Now you've moved to the live server this line could be incorrect. If this is the case, edit the file to Read
RewriteBase /
Chances are it is one or other of these issues - missing .htaccess file or incorrect RewriteBase. A third and nowadays somewhat more unlikely option is that your server doesn't have mod_rewrite enabled - but I think that would result in server 500 errors.
Check whether you are using any modules that is calling database and you have not changed DB details in that module after migration. If admin panel is working fine then I think problem with some modules that are used in front-end. You can do debugging by disabling few suspected modules and check whether your site works fine or not. Else provide some more information about your site so that I can check further.
I have installed drupal on my localmachine(ubuntu, Xampp), at localhost.
Path and Pathauto modules are active (a module to produce friendly URLs).
Migrating/Pushing my local install to the www.mysite.com
Exported SQL from phpMyadmin(localhost).
Made a new DB at live site (I think a different name from the localhost-DB does not create any problem).
Imported SQL into phpMyadmin, (mysite).
Changed the username-password-DBname in the sites/default/settings.php in drupal folder.
Now, uploaded the drupal folder and all its content into the /www of the "mysite.com".
Visited the URL www.mysite.com, site looks same as on my localhost, good.
But --
I made a tryPage on my
localhost/drupal, for which
pathauto(cleanURL) recommended the
URL "content/trypage" which i
explicitly changed to "trypage", so
that absolute link to the page is
"localhost/drupal/trypage" and not
"localhost/drupal/content/trypage".
Now When i click the trypage link on the mysite,
it open's it in-reference to my
localhost, my local-pages are
opened. That is, when I click
newpage on the mysite.com, the URL
requested is
"localhost/drupal/newpage" and not
"www.mysite.com/newpage".
Do you think it is coz of the SEO
friendly URL generation issue, the
Pathauto module.
Anyways how do i solve this
If I make my "localhost/drupal" to open from same URL (mysite.com), i dont know how
to do that exactly, i think by configuring
vhosts. But if i do that, then the URL
www.mysite.com where will it take
me, local or online.
Now If i add new modules, new content, new pages, and new books on my localhost site, and wish to update mysite.com, do i have to redo SQL export/import everytime, and use a software like rsync/sitecopy(), to upload the folders on the live site. How do i solve this.
This is an old question, but here are some thoughts.
Links generated by Drupal (e.g. menu links, links within the admin area, breadcrumbs, etc.) should always use the domain of the currently requested site. URLs within Drupal are handled by the "router", which stores all paths within the database in a relative format.
That said, unless you're specifying the site URL in settings.php (the $base_url variable) or are linking to pages using fully qualified URLs, this shouldn't be a problem. Linking to different nodes from other nodes can be handled with a variety of modules. Pathologic is a good choice, or Path Filter.
Moving Drupal sites from development to staging to production is still a common problem for which there is no definitive solution. This question was asked previously here.