Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest sNews - sNews 1.7 - with its own forums - for discussion and user mods.

Pages: 1 ... 3 4 [5] 6 7 ... 10
 41 
 on: August 10, 2014, 05:30:26 PM 
Started by Edgardo - Last post by Keyrocks
Good to see it helped Ed.  ;)

 42 
 on: August 09, 2014, 06:35:33 AM 
Started by Edgardo - Last post by Edgardo
thenks key, as always you are very very very .... clear and my add clever with your answes. Have a good day

 43 
 on: August 08, 2014, 06:10:16 PM 
Started by Edgardo - Last post by Keyrocks
The [func] [/func] tag-set is for inserting the name of a PHP function within the content of an article or page, so that whatever the function does it will be displayed along with the content of the article or page. Of course, the PHP function needs to be in a PHP file that is already available ... such as the snews.php file in your sNews file-set.

Example One:
Let's say we create a PHP function to perform a specific task and we save the function somewhere within the snews.php file (so that it is enabled and available). For example, this function - nameit - will display the name defined as the value in its first string - $name = '<h2>My name is Edgardo</h2>'; (Edgardo in this example)  wherever the function is called.

Code: [Select]
<?php // ignore the PHP tag

function nameit() {
$name '<h2>My name is Edgardo</h2>';
return $name;
}
define('_MYNAME',nameit());

// ignore the php tag
?>


Next - to display your name within an article or page content, you would put the name of the function within the function-tags in the text-area like this - [func]nameit:|:[/func] - and wherever you put it, your name will be displayed in the <h2> font-size (since the name value is wrapped with <h2> HTML tags within the function itself).

Example Two:
Let's say you want to display a Contact form on a specific article or page. The PHP function that generates the Contact form is already in the snews.php file (by default) .... so you would just insert the function tag-set with the contact form function-name inside the tags like this - [func]contact:|:[/func] - and wherever you put it in the article or page text-area, the contact form will be displayed.

 44 
 on: August 07, 2014, 05:31:10 AM 
Started by Edgardo - Last post by Edgardo
Hi to all, been a long time.. but my mod was sleeping, I have made many changes on the mod before sleep that and worked fine, but my cuestion today is about the function button, the one [func][func] or some like that. Maybe you answer that but cud not find the answer. Is for php functions or may put javascript in there?
By the way one of my mods is to make searchs on comments too, by default just searchs on pages and it works fine, just one thing have to put paginator on 10, it was easy to think on that way, and left that way, maybe changing that harcoded number for the pagination variable should work. if anyone is intrested i will put the code. thenks

 45 
 on: August 06, 2014, 09:39:52 AM 
Started by Tropy - Last post by Tropy
The emoticons are there but if i look in public view they are only :laughing/: any answer?

 46 
 on: July 22, 2014, 03:11:42 PM 
Started by Tropy - Last post by Keyrocks
If you have TinyMCE's default Emoticons plugin installed and activated, check to make sure you have it initiated correctly:
Initializing - TinyMCE Emoticons Plugin

There is also a Smileys Plugin for TinyMCE that may be worth checking out - just be sure that it is compatible with whichever version of TinyMCE you are using: TinyMCE Smileys Plugin


 47 
 on: July 20, 2014, 03:41:50 PM 
Started by nukpana - Last post by nukpana
At the moment, based on this update from a few days ago (link), I am close to completing part B of this "outline" if you will call it that.

I noted here, that moving forward with a 1.x version can be done, it is hard to do.  If you want, this outline is a good start.  You will want to add updating or replacing out cleanXSS as it is getting a depreciated notice (at least for me):
Quote
Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead
Culprit:
Code: [Select]
            $source = preg_replace('/&#38;#(\d+);/me','chr(\\1)', $source);
            $source = preg_replace('/&#38;#x([a-f0-9]+);/mei','chr(0x\\1)', $source);

 48 
 on: July 19, 2014, 05:00:31 PM 
Started by Tropy - Last post by Tropy
the only thing at moment that didn't work is the smileys in tinymce in posted articles

if i want show a  ;D it shows LAUGHING:

how is the prob?

 49 
 on: July 19, 2014, 04:56:55 PM 
Started by Tropy - Last post by Tropy
sorry was my fault!

got something messed up in my code! :-X

 50 
 on: July 16, 2014, 01:38:51 AM 
Started by stjepan - Last post by nukpana
What you describe - I would see it as another incremental development step, maybe to call it sNews 1.8.

But it we were going to go all the way to sNews 2.0, then I would prefer that we re-think the foundation for sNews. It might be similar to the extensive contribution Jason (nukpana) made here, working on (and off) over the last three years ... or it might be a new, fresh start.
Thanks Doug.

I am still of the belief if those want to continue to 1.x line, it can be done, leading into a 2.0 like system.  But the work is hard, I won't kid you.

The next steps would be:
1) Pull a new development team together,
2) choose a project leader to keep us all on track,
3) Draft up a list of guiding principles that we agree to follow,
4) Get started on a functioning core.
I would disagree. 

I think 3 & 4 should be first and foremost and the one doing most of the dev/decisions could be 2.  It would almost coincide with each other. 

Point 1 will come not as a team but like github, where anyone can contribute to the project (via pull & merge requests) and bring up issues.  Look at http://www.slimframework.com/ and you will see the "team" is a group of (I assume) the contributors with the project creator/lead at the top - looking at the project's github page, you can see there is ALOT more contributors and this is what I am referring to.

I'll add that we went through the four steps above a few years ago when we first started discussion a move to sNews 2.0. Our team leader did circulate a rough outine for a new core but was unable to take it any further (due to personal priorities becoming more important). Unfortunately, the rough outline was not functional and none of us were able to get it working, so we never got a good start on the 4th step.
If I recall, there was some debate as well, which also delays development

Pages: 1 ... 3 4 [5] 6 7 ... 10