Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Obake
1
Archived fixes / Re: Notifications Fatal Error
« on April 29th, 2014, 12:05 AM »
:)  Actually that happened here, on this site. Using FF 28 and ad-blockers. Maybe just a one off event? <shrug>



2
Archived fixes / Notifications Fatal Error
« on April 27th, 2014, 01:10 AM »
From the Home page. Clicked on Notifications to see the one that was listed. Clicked on the linky to the thread below.

http://wedge.org/pub/support/8597/change-blurb-on-forum-home-page/msg295610/#new

Edited the thread to add the code brackets to an example, saved the post and this is the resulting error on the White Page of Purgatory ...

Fatal error: Class 'Likes_Notifier' not found in /app/Notifications.php on line 87

Refreshed the page and the thread was displayed and the post had been saved.

3
Archived fixes / Personal Text over running the user profile area ... sometimes.
« on April 27th, 2014, 12:55 AM »
This has happened several times the past week. This time it is in the thread linked below ..

http://wedge.org/pub/import/8350/importer-tool/

See attached images for examples.

The browser is FF 28 and skin is Wilde.  With 14 posts displayed on first entering the thread there are no issues. When clicking for page 2 and then scrolling from post 14 to post 15 the personal text begins to over run its area as seen in the first image. Continue on past and then I get what is shown in the second image.  A screen refresh often clears the issue up.
4
Support / Re: Change Blurb on forum home page?
« on April 26th, 2014, 10:20 PM »
Does not seem to be a simple way but what I had to do was this


Make copies of home.english.php, home.php and home.template.php and name those copies:

MyHome.english.php , MyHome.php, MyHome.template.php  ( or whatever prefix you want )

In MyHome.english.php edit and change the string to whatever you want.

Then edit the MyHome.php and change line 24 from 'function Home' to 'function MyHome'.  ( this part was not explicitly mentioned in the original instructions )

FROM:
Code: [Select]
// Welcome to the show.
function Home()
{
global $context, $txt, $settings;

TO:
Code: [Select]
// Welcome to the show.
function MyHome()
{
global $context, $txt, $settings;


Then in MySQL edit the Wedge db and change the default_index from 'Home' to 'MyHome'.

Purge the site cache and refresh the screen. You should see the new blurb and you will be future proof from updates.
5
Features / Re: Poll: dropping oldIE
« on March 10th, 2014, 02:32 AM »
Quote from Nao on March 9th, 2014, 11:47 AM
What do you think, guys..?
I'm only asking because yesterday I committed an extra set of Bad Behavior rules that actually block any requests made from Windows 95, 98, ME and NT. Windows 2000 is supposed to be in the lot (according to BB's FAQ), but I don't think it is (I would have considered removing it otherwise.)
Win2K was primarily a corporate OS. A lot of businesses used it and a few of us used it on our home PC. I really did like Win2K and it took me a long time to give it up. I really can not imagine any need to keep Win2K out of BB as it is unlikely that it is used by many businesses or individuals at this point. I am sure there are a few, but my gawd, they just need to move on.  :)

6
Features / Re: Poll: dropping oldIE
« on March 10th, 2014, 02:27 AM »
+1 on Bunstonious comment.

Don't support it, remove the fixes for 6 and 7  but also do not block it.

To me, supporting IE 6 and 7 makes as much sense as MS supporting Win 98SE. I worked with a guy last year that was pissed because some AV outfit would no longer support his Win98.  :)  Some folks just refuse to move forward, I suppose.
7
Off-topic / Re: Oh dear...
« on February 23rd, 2014, 12:43 AM »
As an American, I must say that I completely agree.  :(   Dear God, seventy percent of the country are unable to read or write above the seventh grade level. Their attention span is about as long as a CNN or FoxNews news bite, maybe 30 seconds at best. And if given even a tenth of a chance, they will gravitate to the lowest common denominator.

I took down my telly about 6 years ago and have not watched TV since then, other than what I get on the web. For news I go to European news sites. Most of the musicians I listen to are European artists.

My current favorite is Mylene Farmer. Melts my better she does. Canadian transplanted to France.
8
The Pub / Re: Wedge repo -- installation feedback
« on February 3rd, 2014, 05:20 AM »
All is good. Wedge is now installed as a sub-domain. Went without a hitch.  :)

Patience is a virtue I am told.  :)
9
The Pub / Re: Wedge repo -- installation feedback
« on February 3rd, 2014, 03:55 AM »
I think I may need to practice some patients here concerning this sub-domain. Essentially my settings are the same as yours but for my domain. No redirect, built as Type A in Zone, domain is wedge.domain.net, document root is public_html/wedge.

All good as far as I can see but I think I am being caught between sub-domain propgation and the server move. The propgation seems to be quick, about 4 or so hours but later this evening I found the sub-domain had been changed back to the old sub. I think this occurred after the server updated and pushed out the move but some how kept the old sub-domain name. I had previously changed the sub name for simplicty and then later deleted the sub-domain before the server move. That was likely a judgement error on my part. To make it worse, the domains were on one server and the host another. Quite frankly I screwed myself on this one by being impatient and thinking all the propagation had taken place. :)  Anyway, the domains have been moved to the host and I will wait a day or two to give all this time to propgate.

Thanks.  :)
10
The Pub / Re: Wedge repo -- installation feedback
« on February 3rd, 2014, 02:06 AM »
Quote from Farjo on February 3rd, 2014, 12:14 AM
If by a sub domain you mean wedge.domain.tld then mine is on a sub domain without those issues. Maybe it's the sub domain setup?
I used wedge.domain.net/index.php.  As a last resort I even read the Cpanel 11 docs on sub-domain just to be certain.  :)  I still get the same fail at line 21 of OriginalFiles.php. I think I will start up another service and move Wedge to its own space. 

If you have any ideas let me know. 

Thanks
11
The Pub / Re: Wedge repo -- installation feedback
« on February 2nd, 2014, 11:49 PM »
re: skins - Well, all the skins are really good. I prefer the Wine skin because of the color. You did an outstanding job on the color, Nao. A really nice blend of colors that are easy on the eyes. I think that older folks such as myself do not do well with the brighter backgrounds that seem to be popular these days. I think the Wine colors would go well with the Wilde and Wilderless skins.

re: php - well the site was moved to PHP 5.4.24. Still get the same error as before when doing a sub-domain install. I know, I know, you said 5.3 but they moved me to 5.4.  :) 

Interesting though that Wedge will install on XAMPP with PHP 5.5.6 but would not install as a sub-domain there either.

re: Media - I have found that on Firefox the plugin-container.exe needs to not be blocked in a firewall or to have its dom.ipc fields set to false in about:config. Causes issues with mass uploads, and if streaming vids and uploading with the plugin-container.exe set to false the mass upload may or may not work. Anyway, I am sure some already know that but I did not.  :)

12
The Pub / Re: Wedge repo -- installation feedback
« on February 2nd, 2014, 07:10 PM »
re: EOS  .... God, I am a dullard. I knew about PHP 5.3 and still had a brain fart and made the post that I made. Sorry about that  :)

I have played with the software most of the morning. It really is a nice setup. The Wine theme seems to be my favorite thus far.

13
The Pub / Re: Wedge repo -- installation feedback
« on February 2nd, 2014, 05:35 PM »
Am unable to install Wedge as a sub-domain to SMF 2.0.7. I receive this following error

Code: [Select]
Parse error: syntax error, unexpected T_SL in /home/tpforums/public_html/wedge-alpha/core/app/OriginalFiles.php on line 21

this is line 21

Code: [Select]
$file = '<' . <<<'EOS'

Code: [Select]
http://www.wedge-alpha.mywebsite.net/index.php

Host is Charlottezweb and server PHP is 5.2.17.

What am I doing incorrectly?   Thanks  :)
14
The Pub / Re: Wedge repo -- installation feedback
« on February 2nd, 2014, 05:52 AM »
A Time Zone/server issue?

My profile was not set; I then changed it to East Coast/USA and the ' Last Edited' time displayed to me jumped from 5 hours to 17 hours ago. I think I made the post around 7-8 pm USA EST which would be about 5 hours ago.  My time for this post is 11:53 p.m, eastern standard time, USA
15
The Pub / Mass Media Uploads
« on February 2nd, 2014, 12:49 AM »
Quote from Powerbob on January 28th, 2014, 01:33 PM
Nope sorry, I get this error;
I was receiving the same error as you on Mass Uploads.  After removing some ESET firewall blocking for Flash, the Mass Media Upload now works for me  :)

35 files for a total of 9 meg were selected and uploaded. No idea what the behavior is on a live site. From what I have read ( Googled ) this seems to be an issue folks have and quite often it is related to a Firewall.

Firefox 26
XAMPP 1.83 / PHP 5.5
Windows 7-64
Flash Plug-in 12.0.0.43


From the PHP.ini file .... default settings

Code: [Select]
;;;;;;;;;;;;;;;;
; File Uploads ;
;;;;;;;;;;;;;;;;

; Whether to allow HTTP file uploads.
; [url]http://php.net/file-uploads[/url]
file_uploads=On

; Temporary directory for HTTP uploaded files (will use system default if not
; specified).
; [url]http://php.net/upload-tmp-dir[/url]
upload_tmp_dir="G:\xampp\tmp"

; Maximum allowed size for uploaded files.
; [url]http://php.net/upload-max-filesize[/url]
upload_max_filesize=2M

; Maximum number of files that can be uploaded via a single request
max_file_uploads=20

Hope this helps someone.  :)