31
Balzac
Re: How did they do that ?
  • 2010/11/23 11:11

  • Balzac

  • Just popping in

  • Posts: 68

  • Since: 2010/1/11


Link to example?
But I think this is because they have a module as startpage (see admin, preferences) instead of empty and fill it with several standard of selfmade blocks.
As you know and can see lot of modules have those icons on the bottom of the article.
Content, news, xnews and so on.



32
Balzac
Re: User Log In as Main Page
  • 2010/11/23 11:06

  • Balzac

  • Just popping in

  • Posts: 68

  • Since: 2010/1/11


Admin preferences main settings
Choose main page, user profile.
Is user logs in the profile page will ben the main page.

If you mean the login block, see block settings.

See also your question with reply:
https://xoops.org/modules/newbb/viewto ... id=333898#forumpost333898

I see you have a lot of questions. Without being rude, I advise you to experience and explore xoops more before asking everything. Because that way you prevend that other users won't answer your questions anymore.



33
Balzac
Re: Support for Cssified xoops default theme
  • 2010/11/16 13:07

  • Balzac

  • Just popping in

  • Posts: 68

  • Since: 2010/1/11



AWSOME work you do aitor!!



34
Balzac
Re: Publisher module
  • 2010/9/13 23:55

  • Balzac

  • Just popping in

  • Posts: 68

  • Since: 2010/1/11


Thanks, download worked this time.

@rgauci
Cloning the module worked this time like a charme. Btw I had to change the chmod of the module dir into 777 ot run it properly. Afterwoods I changed it back to 755.
And yes I also would like to see this module further developed, because it is a very nice and fine content article module.
To my opinion you cannot compare news/ xnews with publisher (formally smartsection) because there are big differences between these two. Therefore you use them different.
One is news and the other for articles with more 'body' & additions.



35
Balzac
Re: Publisher module
  • 2010/9/13 9:30

  • Balzac

  • Just popping in

  • Posts: 68

  • Since: 2010/1/11


Thanks.
Unfortunately it says the zipfile doesn't excist. I can see it, but cannot download it.



36
Balzac
Re: Blue Move Tip - Search and Replace
  • 2010/9/13 7:12

  • Balzac

  • Just popping in

  • Posts: 68

  • Since: 2010/1/11


And what about
Quote:
Warning: Class 'XoopsTree' is deprecated, check 'XoopsObjectTree' in tree.php in file /class/xoopstree.php line 49


Old modules use xoopsTree.
Should this be replaced too? If yes, how?



37
Balzac
Publisher module
  • 2010/9/12 20:49

  • Balzac

  • Just popping in

  • Posts: 68

  • Since: 2010/1/11


I cannot post within Xoops Module Support forums! Therefore I post here.

In addition to topic Publisher
https://xoops.org/modules/newbb/viewto ... &viewmode=flat&pid=329376

You cannot expect everybody knows how to work with turtoise to grab the latest Publisher svn files.
Since the release of Publisher 1.0 alpha in february 2009, a lot of changes and bugfixes have be made.
So please would somebody be so kind to zip the latest Publisher files and offer them as a total download.

@rgauci
You have cloned Publisher several times. It would be nice if you offer them to the community. Hence not everybody knows how to clone this module. I am sure you make lots of users happy.

I still miss a good content module. Smartsection had potential, but it takes a lot of sources. Also it lacks development.
I had my hopes on Publisher, but unfortunately it I don't see new releases offered by programmers.

Blue Move?

Thanks



38
Balzac
Re: XOOPS Bug Hunting Week
  • 2010/8/23 22:51

  • Balzac

  • Just popping in

  • Posts: 68

  • Since: 2010/1/11


Trabis stated within the newsitem that, apart from security issues, there will be no bugfixes concerning 2.4.5.
Then why focussing on 2.4.5?
I really don't understand this Bug Hunting 2.4.5 thread.



39
Balzac
Re: Voting on the most requested features
  • 2010/8/23 22:17

  • Balzac

  • Just popping in

  • Posts: 68

  • Since: 2010/1/11


Excuse me!
Spitting through over 240 features requests? And after that giving points!
My god, the encyclopedia is thinner.



40
Balzac
Re: "Universal" module framework...
  • 2010/8/4 23:06

  • Balzac

  • Just popping in

  • Posts: 68

  • Since: 2010/1/11


Quote:
Xoops descision was to split modules from the core several years ago. From that moment the module problems began.
Problems because every module developer stumbled up into develop problems because there where core code lacking. Therefore some module developers created their own specific framework. Which in fact is absurd.
One universal module framework can solve this whole module and compatibility mess.


Please Catzwolf, quote all the lines in what I've written concerning this matter.
See the bold line which you left out, where I stated the reason why module developers started to create their own frameworks. Every module developer who creates his own framework for his module to work. And this exactly is what I find redicoulous.
I am pretty sure some code within these different frameworks are the same. And exactly this is what I find redicoulous. Therefore I like the idea melting these code together into one framework.


Since there were talking about the framework proposal, I wasn't talking about how xoops 3, or for that matter 2.4+ is developed and updated.
But if you want to know:
I second (and I am quit sure I've said this somewhere within another topic) that there must not be only one core developer. Open Source is working together, getting involved and be open about core code changes and informed about core code changes.
Getting involved is much more than on a regulary bases asking the community to get involved concerning the repository, wiki and so on (the way mamba keep on doing) but left out for participation concerning xoops core development. This doesn't give the overall spririt back into Xoops. Speciallly not to those who are over the years good and proven trustworthy xoops developers. They were set on a sidetrack which wasn't and isn't good.
Quote:
Don't ask what XOOPS can do for you, ask what YOU can do for XOOPS!

Developers keep asking (for years) what they can do for xoops, but unfortunately they are kept out of the core bussines. For reasons I still cannot understand.
The above sentence works both ways. Or at least should be working both ways. This will bring the spirit back into Xoops as a whole and even more.
For several years xoops development is cripple. And if nothing changes it will stay that way.
To be honest, the recent news release XOOPS Core Development Updates As Of August 1st, 2010 doesn't change much of this core (read X3) development problem. The basic structure, one man, stays the same, which is to my opinion a real pitty.


Don't forget, I do understand the frustration about module development and their developers also developers who have the ability to work on future xoops core but are left out. But I really believe that by creating a solid framework it would be a progression.

As of now I will shut up and let the pro's, if they still feel up to it do their work.
In advance I would like to say thanks for alle your efforts.




TopTop
« 1 2 3 (4) 5 »



Login

Username:
Password:

Lost Password? Register now!

Who's Online

80 user(s) are online (54 user(s) are browsing Support Forums)


Members: 1


Guests: 79


Mamba,

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits