LightWord for Wordpress Home of LightWord Theme

31Mar/1023

LightWord Theme V 1.9.9.2

Hi guys,

Now Lightwordtheme V 1.9.9.2 is online:

Added bulgarian language file (thanks to Marin D.)!

See you

Filed under: lightword Leave a comment
Comments (23) Trackbacks (3)
  1. can you somehow fix ur theme universally instead of having to do it per plugin? the issue is when you have plugins like sociable and YARPP and you have an image that has text wrapped around it, if the text doesnt surpass the image height, then those plugins follow the short wrapped text past the bottom of the image. i have it corrected on my site, but was wondering if you could come up with a universal fix for all post plugins? here is my fix that works if using sociable and YARPP.

    /*SOCIABLE & YARPP EDIT*/
    .sociable {clear:both;padding-top:15px; }

    thanks,
    madLyfe

  2. VoyagerFan did most of the “ugly work”, but others have been committed too. ;] BTW. Andrei – what’s with .com Lightword domain? Have you completely dropped it?

  3. Love your theme,
    im having problems with the drop down menu .. just doesnt work for me.
    Can s.b. please push me in the right direction?

  4. Hello, Valentin again.
    Im using Fotobook plugin to get my Facebook albums which creates a page “Pictures” and the child pages with the according album names. But the child pages are not shown in the Pictures dropdown menu. If i create a page and define it as child of some other page the dropdown menu is created as it should be. Now what can i do? I would be very greatful for your Help.

    Thx Valentin

  5. Hello there… I am noticing a problem with the Calendar widget on my blog. It’s not calculating the first few weeks of the month correctly. You can see it on the right side in the sidebar. You may find it necessary to go back a month or two.

    Also, it would be nice to be able to specify that the week starts on Sunday as an option.

    Thanks for an awesome theme!

  6. hi, yhis amazing theme will be compatible with new 3.0 wp? tnx

  7. Can I pay you to change “lightword” to colors I want to use for my blog/site? If so, please contact me.
    Nice theme!

  8. Ha, indeed. I appreciate the credit. However, Tomasz is correct that others were committed. I certainly wasn’t the only one making suggestions. :)

    My only question now is about automatic upgrade. My WordPress theme manager says that auto-upgrade is “unavailable for this theme”, and the LightWord Settings page doesn’t seem to have detected the new version yet (it says 1.9.6 is the latest version). I will find time to upgrade manually if necessary, but do you have any ideas why the auto-upgrade isn’t working for this version?

  9. Is there any way I can change the cufon font size? its too big compared to previous font. Thanks

  10. Thank for adding Danish translation. A more update version is available here: http://wordpress.blogos.dk/s%c3%b8g-efter-downloads/?did=132.

    My daughter runs your theme and appreciates it!

  11. Hello! LigthWord is the best wordpress theme! Congratulations!

  12. Scratch the starting on Sunday bit… I found how to do that in the WP options.

  13. Sorry.. that was a problem with the WP core itself. Disregard that message, except for the awesome theme part!

  14. I found bug in theme. When disable Cufon cannot click to tab trackbacks

  15. Hi, I am Sorry to bother you. this theme is beautiful, but I met a problem with it.
    Chinese character can’t be displayed, when it’s used in blog title and post title.
    I try to change font to Mirosoft yahei in style.css, but it doesn’t work. (I know nothing about this, just guess), Can you help me? Wish you can understand my Chinese English. :)

  16. Why this theme does not support accents in the titles of my articles. Once a character has an accent, the letter in question is then not displayed.

  17. Hello,

    The French characters (é è ë ê) are not show on post title, how can i fix it?

    Thanks.

  18. hello !andreiluca,
    When I use lightword theme of the 3 Column, I set the show two sidebars, but all gadgets always displays in a sidebar in IE7 。How to solve this problem?
    thank you

  19. Hi,
    How can I remove the dots line below the RSS text in sidebar? Hope you can remove it for the next release. :)

  20. Everyone having trouble with “abnormal” character display in post titles should try changing the setting on LightWord’s options page for Cufon. First see if setting to “Extra” fixes it. If that doesn’t work, the full title should definitely display if you set Cufon to “Disabled”. If disabling Cufon doesn’t work, you probably have bigger issues than a theme malfunction. (Granted, you won’t get prettified titles if you disable Cufon; but if they’re important to you, take some time to hunt up a free font that supports the characters you use and convert it to Cufon format, then just replace the JavaScript files within LightWord’s directory. It’ll be harder to upgrade, though.)

  21. Heh, I was so focused on solving other people’s problem that I forgot why I came here this morning. :P The rest of this comment is @Andrei.

    I tried to use the extra CSS setting in LightWord’s control panel to add the following declaration:

    q {
    quotes: '"' '"' "'" "'";
    }

    Every ” and ‘ was escaped on save, making the output CSS:

    q {
    quotes: \'\"\' \'\"\' \"\'\" \"\'\";
    }

    Needless to say it didn’t work.

    I came to ask if you’d be willing to fix the escaping issue. I’m also curious if you’d consider making the extra styles into a generated stylesheet included with a standard link tag instead of putting the whole block in the header of every page, so they can be cached along with the theme’s default styles.

    Feel free to fix my code examples if they don’t display properly. I don’t know if I can use <pre><code> in comments, and I can’t preview my comment, so I can’t fix them myself if they don’t work. Thanks!

  22. Heh, I was so focused on solving other people’s problem that I forgot why I came here this morning. :P The rest of this comment is @Andrei.

    I tried to use the extra CSS setting in LightWord’s control panel to add the following declaration:

    q {
    quotes: '"' '"' "'" "'";
    }

    Every ” and ‘ was escaped on save, making the output CSS:

    q {
    quotes: \'\"\' \'\"\' \"\'\" \"\'\";
    }

    Needless to say it didn’t work.

    I came to ask if you’d be willing to fix the escaping issue. I’m also curious if you’d consider making the extra styles into a generated stylesheet included with a standard link tag instead of putting the whole block in the header of every page, so they can be cached along with the theme’s default styles.

    Feel free to fix my code examples if they don’t display properly. I don’t know if I can use <pre><code> in comments, and I can’t preview my comment, so I can’t fix them myself if they don’t work. Thanks!

    Also, a note: This is a resubmission of a comment that didn’t appear to go through a few minutes ago. If the original did go through and there’s just a caching issue, please disregard. I hope Andrei will be so kind as to prune this duplicate if that is the case.

  23. Heh, I was so focused on solving other people’s problem that I forgot why I came here this morning. :P The rest of this comment is @Andrei.

    I tried to use the extra CSS setting in LightWord’s control panel to add the following declaration:

    q {
    quotes: ‘”‘ ‘”‘ “‘” “‘”;
    }

    Every ” and ‘ was escaped on save, making the output CSS:

    q {
    quotes: \’\”\’ \’\”\’ \”\’\” \”\’\”;
    }

    Needless to say it didn’t work.

    I came to ask if you’d be willing to fix the escaping issue. I’m also curious if you’d consider making the extra styles into a generated stylesheet included with a standard link tag instead of putting the whole block in the header of every page, so they can be cached along with the theme’s default styles.

    Feel free to fix my code examples if they don’t display properly. I don’t know if I can use <pre> in comments, and I can’t preview my comment, so I can’t fix them myself if they don’t work. Thanks!

    Also, a note: This is a resubmission of a comment and another repost that didn’t appear to go through a few minutes ago. This version omits the use of the <code> tag, which I thought might have gotten the others filtered. If the originals did go through, please disregard. I hope Andrei will be so kind as to prune the duplicates if that is the case.


Leave a comment