with the more tag it is not formatted in the permalink view. that is, you see the code in the full text view. here as in the discussion view. but in teh discussion view that has always been the case
what about removing the 'click to read more' then? although, of course, one can laways customise that.
are you planning to introduce the timezone localisation?
timezone Localization. Once i start my Event Calendar extension. I will learn a lot about manipulating dates and stuff.
we already talked about the More tag. its the problem with the formatter ur using. HTML formatter shouldn't display it. its a valid HTML comment, and it should be ignored and not rendered. I guess i do string replacement and get ride of the more tag from the permalink page
yes, we talked about it. but previously it was not displayed in the permalink view. ckeck out this. it's the previous version. the split is after the first two lines
I've found a minor problem which causes havoc in the crappiest browser ever (IE). I suppose it's an absolute/relative path issue: on my local server, new.png cannot be found. So IE displays its ugly red cross thingy instead of the image, and all blog footers are pushed down, floating above the blog posts and making everything quite hard to read.
expanded and list view like google reader isn't hard to make. but why would u want that. zero u should be able to fix the new.png path. check if new.png is there in the folder.
In theme.Blog.php file Line 37 change it to this $BlogList .= '<span class="BlogNewComments"><a href="'.$NewUrl.'"><img src="'.$this->Context->Configuration["BASE_URL"].'extensions/Blog/theme/images/new.png" /> '.$Discussion->NewComments.'</a></span>';
That's the fault of the extension not of the browser... Sure, but IE screw up everything because of its "image not found" icon while others just don't display the image...
I cannot get the pagination to work with Friendly URLS (even after adding the .htaccess on the first topic). I'm getting:
The requested URL /extensions/2/2/ was not found on this server. Where the blog category is 2, and the page is 2.
Anyone else having this problem?
the URl is fine thats what its suppose to generate something else in ur .htaccess is messing it up. I'm assuming its the code that ur using to make ur blog the default page
What's weird is I removed the DirectoryIndex call in the htaccess, still didn't work, then I removed everything except the Blog htaccess stuff and it didn't work. Kind of puzzled by it.
Just curious if this extension is suitable yet for a non-testing environment? Although, I suppose if mis-one is using it that kinda answers my question.
Comments
it is not formatted in the permalink view. that is, you see the code in the full text view.
here
as in the discussion view. but in teh discussion view that has always been the case
what about removing the 'click to read more' then? although, of course, one can laways customise that.
are you planning to introduce the timezone localisation?
Once i start my Event Calendar extension. I will learn a lot about manipulating dates and stuff.
we already talked about the More tag. its the problem with the formatter ur using. HTML formatter shouldn't display it. its a valid HTML comment, and it should be ignored and not rendered. I guess i do string replacement and get ride of the more tag from the permalink page
zero u should be able to fix the new.png path. check if new.png is there in the folder.
http://localhost:85/vanilla/
All images can be found in :
http://localhost:85/vanilla/extensions/blog/theme/images
But for new.png, it points to:
http://extensions/blog/theme/images
It would work on a live forum, but it doesn't on a local server.
Line 37
change it to this
$BlogList .= '<span class="BlogNewComments"><a href="'.$NewUrl.'"><img src="'.$this->Context->Configuration["BASE_URL"].'extensions/Blog/theme/images/new.png" /> '.$Discussion->NewComments.'</a></span>';That's the fault of the extension not of the browser...
Sure, but IE screw up everything because of its "image not found" icon while others just don't display the image...
something else in ur .htaccess is messing it up.
I'm assuming its the code that ur using to make ur blog the default page