<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>WassUp Forums &#187; Tag: warning - Recent Topics</title>
		<link>http://www.wpwp.org/forums/tags/warning</link>
		<description>WassUp Forums &raquo; Tag: warning - Recent Topics</description>
		<language>en-US</language>
		<pubDate>Fri, 10 Feb 2012 16:29:28 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.3</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>http://www.wpwp.org/forums/search.php</link>
		</textInput>
		<atom:link href="http://www.wpwp.org/forums/rss/tags/warning/topics" rel="self" type="application/rss+xml" />

		<item>
			<title>braeburn on "Warning: temporary files location folder"</title>
			<link>http://www.wpwp.org/forums/topic/warning-temporary-files-location-folder#post-365</link>
			<pubDate>Thu, 24 Apr 2008 15:44:00 +0000</pubDate>
			<dc:creator>braeburn</dc:creator>
			<guid isPermaLink="false">365@http://www.wpwp.org/forums/</guid>
			<description>&#60;p&#62;I updated to 1.5.1 and the warning apear. But it works fine. the same with the version before, I guess 1.4.9. It displays the warning but works fine. I've checked everything, the php.ini the folder , the permissions, change the folder in different locations, full path and so on. but the path and folder taken from php.ini exist, and there are session files in it. So i thought it seems to be ok. just a little bug or something.&#60;br /&#62;
But after updating to 1.5.1 and runnig and collecting for some day's it say it had been stoped in fact of that error. I've tried to deactivate every plugin.&#60;br /&#62;
It's just a day of missing data but i don't wanna check the system every day&#60;/p&#62;
&#60;p&#62;have anyone a clue to fix it?&#60;br /&#62;
I tried this forum and the wiki.&#60;/p&#62;
&#60;p&#62;THX&#60;br /&#62;
WassUp 1.5.1 (1.4.9)&#60;br /&#62;
WP 2.5&#60;br /&#62;
PHP5&#60;br /&#62;
on a root server
&#60;/p&#62;</description>
		</item>
		<item>
			<title>bdchamps on "Lot of warning message on headtop"</title>
			<link>http://www.wpwp.org/forums/topic/lot-of-warning-message-on-headtop#post-54</link>
			<pubDate>Tue, 22 Jan 2008 01:51:39 +0000</pubDate>
			<dc:creator>bdchamps</dc:creator>
			<guid isPermaLink="false">54@http://www.wpwp.org/forums/</guid>
			<description>&#60;p&#62;Hi,&#60;br /&#62;
In first sorry for my english.&#60;/p&#62;
&#60;p&#62;I have the latest version of Wordpress and the latest of Wassup.&#60;/p&#62;
&#60;p&#62;But, look what it is on my header's blog !!!&#60;/p&#62;
&#60;p&#62;--------------------------------&#60;/p&#62;
&#60;p&#62;Warning: session_start() [function.session-start]: open(/mnt/129/sdc/8/a/bdchamps/sessions/sess_ba65106ebcefe2a660f6ba0adefb248b, O_RDWR) failed: No such file or directory (2) in /mnt/129/sdc/8/a/bdchamps/Blog/wp-content/plugins/wassup/wassup.php on line 1159&#60;/p&#62;
&#60;p&#62;Warning: session_start() [function.session-start]: Cannot send session cookie - headers already sent by (output started at /mnt/129/sdc/8/a/bdchamps/Blog/wp-content/plugins/wassup/wassup.php:1159) in /mnt/129/sdc/8/a/bdchamps/Blog/wp-content/plugins/wassup/wassup.php on line 1159&#60;/p&#62;
&#60;p&#62;Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /mnt/129/sdc/8/a/bdchamps/Blog/wp-content/plugins/wassup/wassup.php:1159) in /mnt/129/sdc/8/a/bdchamps/Blog/wp-content/plugins/wassup/wassup.php on line 1159&#60;/p&#62;
&#60;p&#62;Warning: session_write_close() [function.session-write-close]: open(/mnt/129/sdc/8/a/bdchamps/sessions/sess_ba65106ebcefe2a660f6ba0adefb248b, O_RDWR) failed: No such file or directory (2) in /mnt/129/sdc/8/a/bdchamps/Blog/wp-content/plugins/wassup/wassup.php on line 1188&#60;/p&#62;
&#60;p&#62;Warning: session_write_close() [function.session-write-close]: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/mnt/129/sdc/8/a/bdchamps/sessions) in /mnt/129/sdc/8/a/bdchamps/Blog/wp-content/plugins/wassup/wassup.php on line 1188&#60;/p&#62;
&#60;p&#62;------------------------------&#60;/p&#62;
&#60;p&#62;With IE and FF, it's same.&#60;/p&#62;
&#60;p&#62;Can you help me please ?&#60;/p&#62;
&#60;p&#62;Thanks for your help, because I love your widget.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Maggie on "Warning Message"</title>
			<link>http://www.wpwp.org/forums/topic/warning-message#post-6</link>
			<pubDate>Fri, 11 Jan 2008 18:44:05 +0000</pubDate>
			<dc:creator>Maggie</dc:creator>
			<guid isPermaLink="false">6@http://www.wpwp.org/forums/</guid>
			<description>&#60;p&#62;I am getting the following warning in my wp-admin/edit.php&#60;/p&#62;
&#60;p&#62;&#34;Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/.muensterwasher/maggierowanista/rowanista.prettyposies.com/wp-admin/menu-header.php:20) in /home/.muensterwasher/maggierowanista/rowanista.prettyposies.com/wp-content/plugins/wassup/wassup.php on line 1119&#34;
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Awam on "Warning: fsockopen()"</title>
			<link>http://www.wpwp.org/forums/topic/warning-fsockopen#post-3</link>
			<pubDate>Thu, 10 Jan 2008 20:39:46 +0000</pubDate>
			<dc:creator>Awam</dc:creator>
			<guid isPermaLink="false">3@http://www.wpwp.org/forums/</guid>
			<description>&#60;p&#62;Hi,&#60;br /&#62;
i have this error :&#60;br /&#62;
Warning: fsockopen() [function.fsockopen]: unable to connect to fc74d6cb1313.rest.akismet.com:80 in /homepages/8/d221433881/htdocs/awam/wp-content/plugins/wassup/main.php on line 748&#60;/p&#62;
&#60;p&#62;This pluggins is great, have you an idea for this problems.&#60;/p&#62;
&#60;p&#62;Thanks you,&#60;/p&#62;
&#60;p&#62;Awam
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>

