Please login or register.

Login with username, password and session length
Advanced search  

News:

You need/want an older version of sNews ? Download an older/unsupported version here.

Pages: 1 ... 3 4 [5] 6 7 ... 10
 41 
 on: October 03, 2014, 05:19:13 PM 
Started by Brian - Last post by Brian
The vanishing part is my largest fear. I find sNews to be really a versatile package and want to do my best to keep it around but because of the decline in activity with it I am trying to design around wordpress as well since eventually ill want some form of store front any how. This is just one of the first cms's I really got in to working with and want to see it stick around. Its still the easiest ive came across. If anything I can use it for one shot marketing sites or something.

 42 
 on: October 03, 2014, 03:22:19 PM 
Started by Brian - Last post by Keyrocks
Hi Brian:
In the past, sNews development was accomplished on a project-by-project basis when a few Users would collaborate on a specific project. There hasn't been a group collaboration on any project for at least the last 2.5 years (maybe longer) that I am aware of. While there has been informal discussion about working on a 2.0 version off and on for a few years, nothing has really gotten started so the versions of sNews currently available are the same - February 16, 2011 was the last time sNews 1.7.1 was updated.

I had a few projects that I'd been working on over the past few years (off & on) that I eventually wanted to release as updated packages, for single & multiple users, with template switching, but I lost all of my localhost projects this past Monday when my Apache server's primary hard drive crashed and burned. If I can get its contents recovered I will continue with those but - if I can't - I'll continue working with the 1.71 version for simple sites when I need them.

I'm always available to assist in developing a 2.0 version whenever a group of current sNews users wants to start working on something along those lines.

As far as old links in several forum threads going offline, that is to be expected over the years since domains are only active as long as someone keeps re-registering them ... I've let a few expire in recent years as well. This website is currently hosted by one of our original developers - Bob Baker - and I don't know how long Bob will keep it up.

 43 
 on: October 02, 2014, 07:50:34 AM 
Started by Brian - Last post by Brian
Ok I am still making tweaks to http://www.deusuno.com. I actually flipped back and forth between Nibbleblog, Wordpress and Snews to try and make a decision and while it was a toss up between Nibbleblog and Snews I had to go with what I know and push my design. I am still making CSS tweaks and trying to decide on a web font but am hoping to get this thing moving pretty soon. I wish there was a way to take Nibbleblogs admin and use snews together as I want features from both scripts kinda badly which sounds like it may be my next outsource to India project lol.

I still find wordpress too overly complex for what I want to do and the design learning curve is something I didnt have time to deal with.

Now what I am wondering is now that its been a couple years since I asked this. Is sNews as a package still pretty future proof? My fear is  with sNews not seeing advancement of any kind is it possible new PHP versions could suddenly render sNews useless? I want this as my core but am afraid of it just vanishing one day. Ive even been building my own database of every mod and add-on I can find just to have references in the future because sites seem to be going offline and disappearing so much. Even in this forum 99% of the links are dead or wordpress.

I know this is long winded but hope you can make sense of what I am getting at.

 44 
 on: September 24, 2014, 02:51:28 PM 
Started by joaobaker - Last post by Keyrocks
I'm not experiencing any problems on my server running with PHP 5.2.0 (with session support).
Have you checked your php.ini file to confim that mod_rewrite is enabled?

If you haven't already, put a phpinfo.php file in your site's root ... with the following in it:
Code: [Select]
<?php
// Show all information, defaults to INFO_ALL
//phpinfo();

// Show just the module information.
phpinfo(INFO_MODULES);
?>


Then point to the file in your browser http://your-domain/phpinfo.php
And it will display the details of what's enabled on your server. The second function is enabled. If you want to see all of the information, disable the second function and enable the first one.

 45 
 on: September 23, 2014, 08:41:37 PM 
Started by joaobaker - Last post by joaobaker
Hello, well I've had everything working for a while now, and sNews is SO fantastic.

Anyway, I switched my PHP version from 4.4.2 to 5.2.1. BIG MISTAKE. I changed it to run activeCollab which requires PHP 5+.

After switching, sNews won't post my new articles or extra contents, I get the 'Operation Successful' message, but no content appears. Switching back to PHP 4.4.2 all works fine. I know sNews 1.6 and 1.5 say "
PHP: Hypertext Preprocessor version 4.x or above" so I am unsure what the issue is.

I apologize if this has been covered, I did a forum search. Thanks for any guidance.

 46 
 on: September 15, 2014, 12:54:32 PM 
Started by GerryMacOstair - Last post by nukpana
Awesome work Gerry.  I love the site!

 47 
 on: September 12, 2014, 04:38:36 AM 
Started by GerryMacOstair - Last post by GerryMacOstair
Thank you, gentlemen, very kind of you. @sibas: Thanks for adding me to the list. @Doug: Glad, you like it.

Cheers,
Gerry

 48 
 on: September 11, 2014, 06:48:41 PM 
Started by GerryMacOstair - Last post by Keyrocks
@Gerry - I REALLY like your single-page approach using sNews 1.7 and your template (theme) is - quite simply - refreshingly 'outside-the-box'.  Well Done! :)

 49 
 on: September 11, 2014, 09:45:43 AM 
Started by GerryMacOstair - Last post by sibas
Nice one! I like your single page and I added to The list;D

 50 
 on: September 11, 2014, 03:11:33 AM 
Started by GerryMacOstair - Last post by GerryMacOstair
This is an answer of sorts to this thread http://snewscms.com/forum/index.php/topic,9055.0.html by nukpana. There certainly are different approaches thinkable to create single-page websites w/ sNews, but I do think that this one is the simplest (if probably not the most elegant one).
Use "articles" to feed your content to the system (database). Allow as many articles to be displayed on your home page as you need. Don't let the titles be displayed so you have more control over structure and layout. Write the titles and content directly into individual articles, and wrap them with the structure tags necessary to keep the page valid. For the standard sNews package use
Code: [Select]
<div>, for HTML5 variants use
Code: [Select]
<section> and
Code: [Select]
<article>. This way, you are not at risk of making a mess of the engine file (snews.php).

Your various chunks of content will be displayed via the "center" function. You can sort them easily via the "time of publication" feature (which you enable but don't want to have displayed). Add "id" values to your
Code: [Select]
<section> tags (HTML5) or your individual outer
Code: [Select]
<div> tags (XHTML) so you have anchors for the navigation.

If you want a contact form displayed on this same page (which you probably will), create another article, set the time of publication to the earliest date (if you want it to appear at the end of the page), and insert the proper structure tags and use the "insert function" available from the editor. Insert "contact" (w/o quotes) in the first popup dialog and leave the second one empty. Remove the function shortcuts you don't need on a single page website (breadcrumbs/pages/articles/comments/rss links). Design the page with CSS.

That much for the easy part. Now, there is a peculiarity of single page sites that needs some consideration as it usually is not an issue in standard packages. We don't have a single "contact page" that would be displayed, once some visitor navigates to this form. This will cause a fine mess as soon as the form will be submitted. Whether the message will be sent successfully or an error occurred, there will appear a response to inform the visitor as to whether the process was completed or not. This message would appear on the contact page. Since we miss it, it appears in the area governed by the "center function" (where all our other chunks of content used to be). This may cause the visitor to get stuck, especially in cases of failed transmission. The "return" link would point to the contact page we don't have.

To mend this, it is, after all, necessary to fiddle (a little bit) with the engine file. So make a backup of what you already have, and open snews.php in your ASCII editor of choice.
Look for this string
Code: [Select]
function contact() and scroll down until you get to the notification
Code: [Select]
'contact_sent' and remove the word
Code: [Select]
home from this code line so that you have only the two single quotes left. The line will then end in
Code: [Select]
sent'),'');.
The scroll further down to find the notification
Code: [Select]
'contact_not_sent' and remove the word
Code: [Select]
contact, so this line also ends in
Code: [Select]
sent'),'');. Then set your cursor before the semicolon and add
Code: [Select]
.' '.l('message_error'). This will put out a (somewhat) comprehensible choice of reasons for the failure to the visitor. Save the file.
Now open the file "EN.php" in your "lang" directory and find
Code: [Select]
$l['contact_sent'] and add
Code: [Select]
<a href="./">Please reload this page</a> to the message. The go to
Code: [Select]
$l['message_error'] and do the same. This will give inexperienced visitors an easy way to make the page display as it should again.

As it turned out, this description is quite lengthy. This was not my intention. Here's hoping this little tutorial will be useful to someone.
Oh, and if you get stuck with a series of failed message submissions, you might want to try this; at any rate, it did work for me.
Go to snews.php and find in
Code: [Select]
function contact() this line
Code: [Select]
&& $name && $mail && $message && checkMathCaptcha()) { and change it to read
Code: [Select]
&& $name && $mail && $message && checkMathCaptcha==true) {.
Here's visual proof: http://macostair.net/

Regards, Gerry

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