(2013-09-26, 04:55:45)lnickel Wrote: I have one issue that I'm hoping someone could elaborate on. I am using the <?php nm_list_recent(); ?> in a component and making it show in a sidebar

I recently switched on the custom permalink in settings to

%parents%/%slug%/

Now when you click on the list item it doesn't work -where before it had worked

This is what shows and I get a 400 error page.

%parents%/current-views/post/another-test

Any ideas?

Thanks!

(2013-09-26, 15:52:03)Carlos Wrote:

(2013-09-26, 04:55:45)lnickel Wrote: I have one issue that I'm hoping someone could elaborate on. I am using the <?php nm_list_recent(); ?> in a component and making it show in a sidebar

I recently switched on the custom permalink in settings to

%parents%/%slug%/

Now when you click on the list item it doesn't work -where before it had worked

This is what shows and I get a 400 error page.

%parents%/current-views/post/another-test

Any ideas?

Thanks!

Looks like News Manager (and probably other plugins) is not compatible with I18N's own new %parents% placeholder, because of the way it's done. I'll do some tests and prepare a patch. What plugin version are you using?

You say it happens with the sidebar recent posts lists. Can you confirm this issue also happens with posts in the main news page? (it happens to me)

(2013-09-26, 17:36:55)lnickel Wrote: Right Carlos. It happens in both the excerpts (main page) and the recent lists in the sidebar.

I'm using News Manager Version 2.4.4

Along with I18N and the other I18N plugins (custom fields, special pages)

Its not imperative for me but I just to point that out Thanks!

(2013-09-22, 05:00:10)TeeJay Wrote: I also want to ask you if you could include the dimensions filled in in the back-end to the "width" and "height" attributes of posts' images- it would be perfect.

(2013-09-28, 01:27:31)Carlos Wrote: NM currently uses the (GS) news page's meta description only for the main news page, not for posts (which, by the way, don't have a description field). I did it (since 2.4.0) to avoid duplicate descriptions.

As for meta keywords, both the main news page and single posts share the same ones - those defined in the GS page. I don't care much about this, given that google doesn't use them, but if some of you would like to have this, I could add some setting.

(2013-09-22, 05:00:10)TeeJay Wrote: I had little troubles comprehending all the settings at the first look and I think that if I haven't worked with NM before, I would have much more troubles. Furthermore, there are no articles used. I'm also not a native English speaker, but I think I can contribute a little.
[...]

(2013-09-22, 00:01:18)D.O. Wrote: then here is the CSS solution for showing date and author on the same line:
...

(2013-09-22, 00:01:18)D.O. Wrote: Btw, I look forward the author support will be ready!

(2013-09-28, 03:42:57)Carlos Wrote: I'm adding optional post authors for the next beta (though you'll have to use gsconfig + components settings to enable this).

I am thinking about enclosing the author name between some html tags, so that they can be styled.
How about using <em> ?

Code:

<p class="nm_post_author">Author: <em>username</em></p>

(2013-10-02, 16:38:55)D.O. Wrote: Hi mates,
You know, I found with pleasure my CSS easy solutions for NM.

PHP Code:

<p class="nm_post_author">Author: <em>username</em></p> 


Frankly would insert <span></span> instead of <em></em> but if you prefer to use it in this way, then the CSS code could be like this, e.g.:

PHP Code:

.nm_post_author em { text-transform: capitalize; color: red; font-style: normal; } 


Same thing for <b></b> in meta, e.g.:

PHP Code:

.nm_post_meta b { text-transform: capitalize; capitalize; color: blue; font-weight: lighter; } 


In the end, <em> is okay to me. That's all.

(2013-10-03, 03:12:44)Carlos Wrote: I meant this:

PHP Code:

<p class="nm_post_author">Author: <span>username</span></p> 


(2013-10-02, 23:18:35)lnickel Wrote: span tag would be better. It's less presentational. You would have more ability to style.

(2013-10-03, 15:39:48)Carlos Wrote: I agree with TeeJay. Back to <em>

As for changing the default html tags for post titles, I'm thinking about adding an (advanced) setting for this, like markuptitle, that would allow to have e.g. <h3> as default, but <h1> for single post view.