Yep, thanks to Mithrandir and maciek for the help. That was exactly the problem. Few modules that I had installed and removed later remained in the blocks part.
Problem solved.

Same here. Even after upgrade to 2.2.1 no improvement. This is really annoying, since without block management and missing blocks on the font page, the page concept has been messed up badly.
Any help is highly appreciated.

Quote:

I have the exact same problem, but can't figure out what may be causing it. Any hints or pointers are appreciated.

Hi All,

Possibly after a crash on the server side or after a MySQL upgrade all of the sudden all albums in my gallery are empty. The top info bar says that I have 900 pics, but they are not shown in the specific albums and all albums are marked as empty. The random pic and the most recent pic modules however, are able to show the pics.
The database tables seem to be alright. I can create new albums and I can also upload new pictures, only the old ones are not shown anymore.
I am using XOOPS-2.0.6 with xoopsgallery-1_3_3_2.
I have had this problem earlier, but don't know anymore what I did to solve the problem. Any help is highly appreciated.

Thanks in advance.

Thanks for the replies so far. I had looked into Tiny Content and Free Content but didn't like any of those. It was a while back, so I don't remember the reason
I may try those again and I will be looking into the other suggestions too.

I should also add that what I have in mind, is something like the add link feature of the Mambo Server. It enables you to determine the hierarchical link structure of the menu and the content of each link. It is a great feature.

Thanks.

Hi,

I need to add frequently new pages to my XOOPS site, which need to be linkable from a menu. Either from the main menu, or from a menu ins a block.
Right now I am doing this handish. I am wondering which module is best suited to automate this? The "Sections" module wouldn't be the right thing.

Thanks.

I am not sure if I understand the question about the other scripts. But if I get it right, for a correct HTML rendering you need always the explicit LTR or RTL attribute in your tags. Just using UTF-8 won't work.

And thanks, it would be very useful to have these tags inside XOOPS core. As long as it is there and it renders correctly, it is fine with me :) no matter if it is inside table or somewhere else. In fact, I have noticed that Mozilla has a problem with rendering these mixed contents correctly. This might have something to do with the fact that we use it in 'table'.

Quote:
Yes, this is exactly what I mean. The multinlingual hack "sorts" content based on the interface language which can be choosen from a drop down list. But this is only one issue.
Important for us is to be able to mix content. Our site for example is in English only, but we use a lot of Farsi content and in the same post we mix RTL and LTR. Our hack enables us to do this and just this.
But even the multilingual hack that you mentioned still needs this tags IMHO. Because RTL users need to be able to post a News, let's say, in Farsi to be sorted under the Farsi interface of the site, but at the same time they are mixing in that post RTL and LTR. Which means you need to be able to tag the interface language and the text direction.

Since this hack of ours is little and fits well within the XOOPS concept, so I think, is there a possibility to add it to XOOPS regardless the progress of the multilingual hack?
Thanks a lot for your attention.

Thanks for taking this matter up.

I think, we have to differentiate between two distinct areas concerning RTL scripts:
1. Site layout and language/script
2. Content: i.e. news submissions

To 1: In order to make things easy, I would like to see this setup during the installation procedure. A question about the language or direction of the site would add a dir="RTL" to the main tag. A pre-requirement for this to function correctly, would be the UTF-8 setting.
Something like this could be done.

To 2: But this doesn't solve the problem of news submissions, comments and posts to the forums. There you might still have LTR and RTL content mixed. Here the tag that I mentioned would be enough, I would not use language specific tags, because it is not necessary. The character set that you are using is handled by the charset setting of the site, stylesheets and fonts specified. The only thing needed, which AFAICS is common to all three or four RTL languages is the direction. So a [rtl]test[/rtl] would do just fine for Farsi, Hebrew, Arabic and other Arabic script using languages (which Farsi is one of).
You are right with language specific tags in the event that this feature is going to be added to XOOPS anyhow and it would be added for these language because of the direction. Otherwise i see in it more of a complication rather than a simplification.

Hope this helps.

Few days back, I tried to start a thread with regard to right-to-left (RTL) content, which unfortunately went off un-noticed.

We are using the little hack mentioned in that thread successfully on three XOOPS powered sites and are happy to be able to post in Farsi and English. If you want to see some samples, feel free to browse through the news and forums of our site. I think that using square brackets is a good method to support different scripts. And I would wish to see UTF-8 set as the default charset:

We even have a little hack somewhere to add a button for RTL text so that the user doesn't need to type it in everytime.

I am happy to see this thread now. It is time for XOOPS to offer some multilingual features, and adding the general concept is "very" simple, at least from my POV and understanding.

Thoughts and feedback are welcome.