I just switched over to the beta, and it seems to ignore the setting for 'Enable Post Pages'. I do NOT want my posts on individual pages -- I have it set to 'NO', but now it publishes them all regardless.
Independent of your comment -- if it's an 'option' to Post pages or not, the option should work instead of just ignoring it.
I can't see what the 'big advantage's and fuss over Post pages is. Maybe i'm just old school, but I don't care that each post has it's own web page so it's easier for search engines, etc. and I don't care about conditional tags, and I don't have comments enabled, and I don't use entry titles. -- so all I end up with is several year/month/ugly_long_post_name.html files and a whole bunch of /nopub/############ files created that I don't want or need. Plus the individual post pages aren't visible (world readable) anyway because of the way the unix file permissions are set up on my website.
I agree... I have had my blog for years... now I have all these yearly files/ with EACH day in them... it takes up way to much room on my domain. Is any attempt at fixing this issue being done? Or is "ignore it" the only answer we're going to get?
> It is a big disadvantage for Post Page not to be able to be displayed, > Why would you want to disable post page?
How is this relevant? Personally, I only use the archive pages, and people can still get a page for every individual post. How? I have a script keep a lookup table for every post ID, and when people request a post, I let another script access that table, open the appropriate archive file, and extract the post from it. Saves me a lot of disk usage, and it doesn't introduce much overhead. Post pages are only necessary for people whose web site consists of static content.
Regardless, my blog is also suffering from this problem, and I'd like to see it fixed.
Any news about this issue. It would actually be nice to hear from someone related to blogger. It seems to me that the people publishing their webpages via-ftp on different hosts from blogspot aregetting hit with this new blogger version. Too bad I can't go back to the old blogger.
Still no fix. Still no listing in Known Issues or Blogger Status. This has been going on for over a month, and meanwhile the new version has been declared non-Beta. Is this how world-class programmers approach an easily-identified bug, by ignoring it?