I have been attempting to migrate some Drupal content into another site. So far, everything was working... let's say, fine. You can imagine I have been moving so many things that, I was certain I was going to screw up at some point.
This morning I started getting a "page not found" in my front page. I went to "Site Information" and front was correctly referenced. I temporarily changed "mysite.com/front" to "mysite.com/node" and now, every time I want to return the path to "front" I get an access error and I get a "Page Not Found" in my front page. I have developed the habit to clear cache every time I do almost anything.
What would be the most common reason for this msg to appear? Read/write permissions somewhere?
I am using Drupal 6.2 with several modules and a custom theme, based on Zen.
Laxman13 above brings up a good point. You were previously pointing the front page to the path "front" -- what node or function uses that alias?
If you go to admin/content/node you'll see all content -- are the nodes that you're expecting to appear on the front page there?
Are you logged in as UID=1 when you are doing all of this? If not do you have permissions set for anonymous users to view the content in these pages?
Related
I migrated the company's website on a new hosting server. Since then, I cannot access my Wordpress dashboard when I'm logged in.
When connected, I see my website and the classic Wordpress top bar. But when I click on the button with the name of my website (usually that sends me to the dashboard) it just sends me back to the home page.
I add that the top bar isn't really like the classic top bar since it doesn't contain any option.
Here's a screenshot.
The top of my website when logged with the top bar of the admin wordpress
Clicking "Bonjour Signature_Beta" doesn't do anything. I can only log out.
Going to the /wp-admin page gives me an error saying "Sorry, you do not have authorization to reach this page". Except, I'm supposed to have authorization since my profile has a wp_content value of a:1:{s:13:"administrator";b:1;} and wp_user_level of 10.
I have tried multiple things I found online that didn't come to fruition sadly :
Renaming plugin's folder (nothing changes except page breaking because they're made with Elementor)
Renaming theme's and child theme's folder (page goes blank, top bar still there though)
Replaced .htaccess file (nothing)
Checking my account didn't lose admin privilege through phpmyadmin (it didn't, it's at level 10 + it has the weird administrator code
Added a new admin account through function.php (can log in with it, still can't access dashboard)
Increased memory limit
Repair database tables
Kind of desperate and frustrated about it.
Thank you in advance for the help :)
Ok with a fresh pair of eyes, I found out what was the problem. Tables prefix! I followed what was described here : After moving Wordpress, login works, but no admin access anymore
For the record, I never found it when googling or searching my answer here before posting. When posting my question I review the post stackoverflow suggested and it wasn't there either. But now it's suggested next to my post, so... great!
Hi I'm having an issue with a site where visitors need to be members to access certain pages, but once logged in they go to these pages and still see the 'not logged in' page and need to refresh to view the actual content.
This obviously leads to a lot of bounces and I'd like to fix so that they see the content right away.
The root issue comes from some cache settings or something from the host - unfortunately we can't change host (and it's not a regular hosting company with a website but a design company reseller) for the time being. This issue does not occur in our offline environment of the same site.
I've already had to add a ?randomnumber to the stylesheet so it loads new versions properly. I was wondering if something like this would work - but dynamically as pages are being added all the time by different admins.
Or any other solutions also appreciated!
Thanks
Like you said, tweaking the caching settings would be the most ideal. But since that's not an option, I'd suggest adding a random, meaningless query string to the URL of the member pages so that it's seen as a 'new page' and (likely) won't cache.
So instead of /member-page
Direct them to /member-page?cache-buster=randomlyGeneratedStringHere
Drupal 7.19
Acquia hosting
using Yottaa for optimization and monitoring
Problem: when trying to log in from home, we're experiencing something odd: we keep getting "logged out" ONLY on the front page. When you click anywhere inside the site, we get the admin toolbar and contextual links back. But we can't update the front page at all because it acts like it's logged out only for the front page.
This only happens when we're at home working on the site. This does not happen when we're in the work office.
Anyone experienced this? Don't know at what level is this occurring in...drupal, yottaa?
Found out the issue. It was a specific caching for the homepage on Yottaa's CDN. Once I turned this off, I was able to edit the home page again.
Note: They said that turning it off is not recommended. Instead, they recommend to flush the cache. Either way, found out what was causing the issue.
I'm trying to mask a page URL in a Wordpress installation. Let's say it's http://www.mysite.co.uk/wordpress/page and when this page is opened, I want the URL to show http://www.mysite.co.uk/wordpress/anythingelse. The whole point of this is so that the URL cannot be shared, only accessed by authorised users, which means I also want it so that you cannot access this page by typing in /anythingelse. Is this possible and how do I go about this? I've got as far as .htaccess files but I have no experience working with this...
If you use http://www.mysite.co.uk/wordpress/anythingelse/ to actually show http://www.mysite.co.uk/wordpress/page, then it means that you will be able to access http://www.mysite.co.uk/wordpress/page by reaching http://www.mysite.co.uk/wordpress/anythingelse/...
You might be trying to do this the wrong way. What is the point exactly? Do you know that in WordPress, you have two ways of protecting pages? One is to make it "Private" (just above the Publish or Update button) and the other one is to make it "Password protected" (same area).
In any case, if you don't use a password but just play with the URLs, it will only be protected as long as the URL stays unknown. Anyone actually typing the right URL will, indeed, be able to access the page.
You can also restrict access by IP. Try to be more explicit about why you want to protect this page.
I am trying to set up a new custom post type and create a page (based off the custom post type archive template) and keep it private until it's ready to be published. I created a page and made it private, but it was visible to everyone (although not in the dropdown like it normally would be, just from entering the permalink URL). So I deleted that from the database (in phpMyAdmin) and tried again just leaving the page a draft. The permalink URL still shows the page template for the custom post type archive. I deleted the draft in phpMyAdmin and still the URL shows the page template (should be giving a 404). I tried this in a different browser where it had never been opened and it also gives the page template.
Does anyone have any idea why this is happening? Why isn't it working to privately publish and why aren't the deleted pages going away?
You propably only deleted the content of your page, but there are more relations to the page. See the database diagram on wordpress how posts are connected to other tables in the database as well. You'll have to delete every record pointing to that post!
I really recommend you not to play around in the database of wordpress, there's a reason why WP gives you the opportunity to administer everything in their admin panel!
To leave a page/post invisible to others, just don't publish it! As a draft, no one can access it unless he/she has access to your admin panel and the required rights to see drafts!
As soon as you publish it - it's published. You can also just use the preview view to see how it would look like! Why your private page was visible to everyone is another question, maybe you made some mistakes with your DB...hard to reckon without any further information. Try to set it up as a normal post/page and publish it privately, log out and see what happens!