61
aph3x
Re: Lets shrink XOOPS
  • 2010/1/25 22:41

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


I know :)

Also if upgrade logs are up to date on the work of the core might be considered an "upgrade package" which will upload you just the stuff that's been modified + extra files if any, which will also save you some grief of several mb to upload; and a full package for new installs



62
aph3x
Re: Lets shrink XOOPS
  • 2010/1/25 22:32

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


One thing...if they can do it then i don't see why XOOPS can't...since current core dev team is working in inherited code, might be that interaction between editors and XOOPS wasn't done the best way back in the days so with time, core bits and pieces are due to be revisited.

Don't get me wrong, me like trabis... don't need a fancy editor as we write all the codes from memory and all tags and such, so missing the wysiwyg won't be a big deal for most of us. I'm simply giving you scenarios that i had to face in the past



63
aph3x
Re: Lets shrink XOOPS
  • 2010/1/25 22:24

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


@ bjuti,

being a XOOPS user i really can't tell you how WP does it ...i don't like WP..nor Drupal..nor Joomla :-p



64
aph3x
Re: Lets shrink XOOPS
  • 2010/1/25 22:18

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


@trabis,

I had a dutch user who didn't see any of the buttons in the editors on his site, while from my end the editor was looking fine. His local language was set to nl on computer, site was default in english as was just installed and no additional files where added...we uploaded nl.js in the editor and all was fixed in an instant



65
aph3x
Re: Lets shrink XOOPS
  • 2010/1/25 22:13

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


@ Balzac,

that's what i mean...since removing the lang files if virtually impossible without modifying 3rd party editors because modifying them will make their upgrade process bit painful for core devs, ONE wysiwyg editor should be chosen and distributed in core rather 2-3 whatever the number is now



66
aph3x
Re: HOW TO CREATE LOGIN PAGE
  • 2010/1/25 21:55

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


modules/system/templates/system_siteclosed.html

alternatively

themes/your_theme/modules/system/system_siteclosed.html

When you edit templates first make a backup or original file so you will have a fast rollback just in case. Go in preferences/general settings in admin and activate the direct check of templates for modifications so you won't loose time emptying cache by hand via ftp

if you're used to smarty and XOOPS then you'll know your way around the file, if you're only used to HTML then the stuff you don't understand what they mean are smarty and most of them are self explained such
<{$lang_siteclosemsg}>

which obviously reads as "site closed message lang constant" or something like that with the same meaning :)

good luck



67
aph3x
Re: Lets shrink XOOPS
  • 2010/1/25 21:47

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


I told you 3 posts ago why we can't do that, i gave a doable solution 2 posts ago :) , alternatively 1 wysiwyg can be chosen as part of core default install



68
aph3x
Re: HOW TO CREATE LOGIN PAGE
  • 2010/1/25 17:34

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


if you also don't want to give users possibility to register then here's the simplest way.. preferences/general settings :Close site, edit your message and select groups allowed to login while site is closed which in this case will be webmasters and registered users and thats it, you have a splash screen which only has login box but where already registered members can still login and to their thing :)



69
aph3x
Re: Lets shrink XOOPS
  • 2010/1/25 17:23

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


A different, better way to do it will be to don't force users to install those...put them in the package but offer option which to be installed and not only as is now which to use.

There are some who use the wysiwyg editors on their site and there are some that don't, my last 3 client sites use only the wysiwyg cause they do something that simple dhtml doesn't..format from word or any other doc production which adds special formatting tags.

So might be like this, add a new admin feature "manage editors" where you get the option which to install and which to activate as well as which groups can use this or that editor. That way you're not forced anymore to install all together and install can be done without where needed/wanted



70
aph3x
Re: Lets shrink XOOPS
  • 2010/1/25 16:52

  • aph3x

  • Theme Designer

  • Posts: 834

  • Since: 2004/12/26


again, no :)

you're right there are many many languages but software's concern is only the ones that serve as a base language for OS and not all languages benefit of that, this limitation has only to do with what one might have default language on its OS. In my case like in yours probably, OS doesn't comes in my language so is set as english which is the best foreign language i speak which will not affect me if langs were to be removed from core editors




TopTop
« 1 ... 4 5 6 (7) 8 9 10 ... 38 »



Login

Who's Online

242 user(s) are online (156 user(s) are browsing Support Forums)


Members: 0


Guests: 242


more...

Donat-O-Meter

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

Latest GitHub Commits