gazouteast

please post line 16 of your vars.php file – it might be possible to identify the fault once its known what it’s calling.

LenK has a good point, but also see https://www.ads-software.com/support/topic/344953

scribu – it’s not a thesis problem directly – it relates to the changes and deprecated functions in WP 2.9 – see this thread https://www.ads-software.com/support/topic/344953

Scribu – this time around that won’t help

Shivendu & djsteve – refer to this – https://www.ads-software.com/support/topic/344953

Basically, you’re going to have to rewrite your themes, and your feed configurations & feed plugins if you’ve anything except default pumping out your feeds.

Gaz

If you search with Google for Open SOurce Model Agency website script you will find quite a few options, and I remember some time ago seeing one that was for WordPress in the form of a premium theme with additional plugins for handling at least a good chunk of what you’re asking for.

Once you have the basics, getting them extended to add more function is fairly straight forward if you employ freelance programmers, which you can do from a number of sites including from the correct section of the WordPress forums.

Have you thought about WP conditional tag is_sticky() ?

Having a post for each season that is a mini site map subsection for each seasons posts, which you then set or unset as sticky so it pops to the top of the site, is a quick and easy solution for visitors but wouldn’t help your email and feed subscribers.

But there was a plugin a while ago “one year ago today” or something like that, which surfaced posts based on a set period in the past. Again, great for visitors, but not for subscribers.

In WP 2.9, you’ve got the new taxonomy and date based conditional tags for pages, and if you examine their coding in wp-includes, you might be able to figure out a way to code custom functions for posts.

I suspect you’ll have to roll up your sleeves and do some custom coding though … maybe something on this structure (obviously this is not the code itself)

get date
find posts with date(M)
while have posts with date (M) create $seasonals=array(the title, the excerpt, the date, the tags)
create post(title=”Seasonal posts for month” date(M), content=$seasonals)

That’s VERY rough but it gives a frame to start from. You might even have to drag in functions from the RSS side of WordPress or from PressThis to get it to grab data / create the post. You’d likely want to run it from a cron job too to automate it, leaving you to get on with writing new content, and letting the system throw up the seasonal post lists.

Alternatively – and this is a bit of a hack – using WP 2.9 create a dozen pages in the format page-january.php page-february.php etc
Set them with the basic template content of index.php but for each month filter the posts returned by date to only show past mosts from the same month.
Then, run a home.php to override index.php and in header.php set an “if / elseif” sequence to call the relevant page-month.php template page based on current date.
Using this method, you could seasonalise the appearance of each page too, with varied graphics etc.

Hope some of those ideas work for you to find a solution.

Gaz

# Version: 3.5.1
# Other Versions ?
# Last Updated: 2008-7-29
# Requires WordPress Version: 2.5 or higher
# Compatible up to: 2.6

There were a LOT of core changes in WP2.7

While everyone here is focussing on the front end theme, I’d also like to throw thoughts in about the admin theme.

Basically, I hate it.

<rant>
Since WP 2.5 the admin side has been awful – it’s way too slow to load as a page, and opening a sub window, such as the media gallery, fries my CPU and takes forever to load – this has been an increasing problem in every sub-version of WP since 2.5 was released.

Lighten up the admin theme, make it load and run as fast as the front end. Just as an example, I’m a fairly fast typist, and there are times when I’ve written something and realise I wrote it wrong, then go to backspace delete and look to the screen to see how far back I have to delete, but the screen is still “writing” what I’ve just typed. Trying to backspace delete over it renders a one character movement per second or longer. This does not happen in the front end comment box, nor on other sites such as here in the WP forums – ergo, it is a problem with the admin theme.

Another factor that makes me hate the current admin theme is all the widgetised stuff throughout – I want to set my admin and leave it, losing the bandwidth, page-code, and rendering overhead of all that java (or whatever it is) so that I can work FAST, not be always waiting for wp-admin to catch up with my keyboard or mouse.

In admin, I want TWO sidebars – one with the existing menus, and another with a menu list I can define and hard code (if that’s the only way to do it) without squishing the admin screens into a single column of widgets – cascading includes would run faster and be just as efficient – the second sidebar could also be used for plugin developers to add micro-help comments, tips, links etc on the individual plugin admin pages, as well as for admins to have a “quick view” of current site activity – users online, posts being read, comments just posted, and in multi-author blogs, posts just submitted or published – these don’t have to be live updating via javascript, just refreshed with a DB query on each page load.

Right now, the biggest offput with WordPress is the “slug on Prozac” symptoms of the admin interface. I know some of you will say it runs fine for you – but what computer spec are you running? If WP needs a dual-socket quad core Intel 3Ghz+ with 16Gb RAM and SAS drives ON THE WORKSTATION PC, with 16GB+ internet connection, to get tolerable performance from the admin screens, then not only should that be stated in the pre-install documentation, but the developers need a good hard slap around the head for not thinking about the planet’s majority of users who are still running 32-bit computers with single CPU, 512Kb RAM (or less), with 8Mb graphics cards and sub-100Gb older and slower hard drives, running sub-2GB internet connections.

The connection and hardware specs needed to get wp-admin to run at reasonable performance is marginalising WordPress outside the north-western quadrisphere of wealthy-nation propellor-heads – think about this BEFORE releasing WP v3.0 – PLEASE!
</rant>

—

Regarding the revised theme for the site’s public side – my requests are simple and already stated by others –
– child themes of similar nature to BuddyPress, but easier to understand and implement, with compatibility with BuddyPress regardless of whether originating in WP or WPMU.
– heavily commented css and php files so users and developers know what each part of the file is attempting to do.
– easily identified and compulsory options for fixed width or fluid (not all theme layouts are compatible with fluid width when the user has a “small” monitor).
– FIVE default sidebars pre-defined and included – header, footer, each side, plus a horizontal “in-content” sidebar.
– multiple page and post templates (e.g. with / without sidebars, single & multi-column) to show this is a major feature of WP.
– both home.php and index.php as standard files in the default theme (they’re needed for WPMU and BuddyPress anyway, so why not include them in WP standalone?)
– post auto-thumbnails, with thumbnail size either settable on the fly when posting (custom fields?) or definable from a post-page panel.
– more “wrapper” divs as standard for background graphics and colours (I know how to do this myself, but how many newbies do?) with a simple options page in admin and the css pulling the data from that.

I could go on, but many of my “wants” are certainly in the plugins or theme customisations arena, and should not be in core code.

Gaz

I’ve tried playing with these and can’t get them to do what I want

In essence, what I’m trying to do is with the top of the sidebar, I want (plain language coding) –

if (is_home()) OR if not a user
~ do this ~
then
~ this ~ (if user or not)

I can get it to work with the is_home command() on it’s own, and I can get it to work with the !is_user_logged_in() on its own, but when I try to run the || (or) php in the middle of them I get a T_syntax (OR) php error and the sidebar fails to load.

It’s starting to drive me nuts because I want the condition to simply be –
If it’s the home page or it’s not a logged-in user (on any page or post), then show the sign up form

Why is this so difficult?

Can anyone help this grump old geezer?

Yup – I just got hit by this as well. It hit me within 20 minutes of upgrading to WP 2.8.5 (the theme had been on the server a couple of days but unused or looked at).
– first I knew about it was an email from my hosting service saying they’d suspended by account due to server abuse (all I had done was leave the Theme editor open and the Home page view open (both on the magazine basic theme) while I popped out to the shop and back.
– the tech file they included with the email has the following data (if it helps anyone)
– hundreds of entries like this one (this one obfuscated where necessary) –

username 14801 5092 1 08:46 ? S 0:00
/usr/bin/php /home/username/public_html/domain_scriptlab/WPdev/index.php
DOCUMENT_ROOT=/home/username/public_html
GATEWAY_INTERFACE=CGI/1.1
HTTP_ACCEPT=*/*
HTTP_HOST=www.domain_name.com
HTTP_USER_AGENT=PHP/5.2.10 PATH=/bin:/usr/bin QUERY_STRING=
REDIRECT_STATUS=200
REDIRECT_UNIQUE_ID=St8CqdB0PlIAABPkY2IAxxxx
REDIRECT_URL=/domain_scriptlab/WPdev/wp-content/themes/magazine-basic/uploads/Home-Banner.gif
REMOTE_ADDR=xxx.xxx.xxx.xxx REMOTE_PORT=46124
REQUEST_METHOD=GET REQUEST_URI=/domain_scriptlab/WPdev/wp-content/themes/magazine-basic/uploads/Home-Banner.gif
SCRIPT_FILENAME=/home/username/public_html/domain_scriptlab/WPdev/index.php
SCRIPT_NAME=/domain_scriptlab/WPdev/index.php
SERVER_ADDR=xxx.xxx.xxx.xxx
SERVER_ADMIN=webmaster@domain_name.com
SERVER_NAME=www.domain_name.com
SERVER_PORT=80
SERVER_PROTOCOL=HTTP/1.1
SERVER_SIGNATURE=<address>Apache/2.2.13 (Unix) mod_ssl/2.2.13 OpenSSL/0.9.7a DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at https://www.domain_name.com Port 80</address>? SERVER_SOFTWARE=Apache/2.2.13 (Unix) mod_ssl/2.2.13 OpenSSL/0.9.7a DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 UNIQUE_ID=St8CqdB0PlIAABPkY2IAxxxx

Anyone got any clues what any of this could mean? They say they’ll re-activate the account (when they get around to it) but I have to delete or fix the offending script within 24 hours, leaving it disabled until I do so, or they will permanently ban me.

Thanks in advance
Gaz

Got same issues as frioman on ALL plugins – both during upgrade and during new install … and I’m on WP 2.8.4

That said, it is only one of my many sites that are suffering this – but still completely beaten by it.

I got the problem that the plug-ins auto eupgrade is asking for FTP user login, accepts the details, then just hangs during the unpacking stage

I tried resetting wp-content to 775 permissions as per another thread – that worked for one plug-in upgrade, then it went back to the same old error.

Changing the actual plugin folder to 775 as well as wp-content, did not fix the problem.

So I tried to get Core Control via the plugin installer … and ran into an identical problem – asked for login, starts unpacking and hangs

I’ve searched WP forums and there are hundreds of threads about this – surely the central devs have an “official” fix for it somewhere?

I’ve got a bucketful of WP installs, on three continents, with a bunch of hosting services, and so far it’s just this one install with the issue (it’s wp 2.8.4 so latest version, and this issue surfaced as far back as WP 2.5 but is unresolved – that’s four major sub-versions it has existed within).

Gaz

similar problem here as explained in https://www.ads-software.com/support/topic/274928

WP 2.8.x doesn’t seen to like calls to javascripts or php scripts outside of its own /js/ folder

This will bring tears to affiliate marketers when it starts breaking their adsense and other scripts

Gaz

I too would like an answer to this question

Situation – I have a WP 2.8.1 install in a folder under home. I also have an osCommerce install in a folder under home. I have a simple 3 file addition for osCommerce (comprising a css file, a modified info_box file, and a php script file).

On an html page on any website I simply add a standard ‘<script src=”blah” type=”blah></script>’ tag and the data shows up.

On WP on the same site, inserting the script tags into a page template causes a content no-show problem, but FireBug reveals that the script output is indeed present in the page (as a line-numbered text list between the script tags).

However, if I change the script tags to make it a php include statement, the content then does indeed show, but with a server error immediately above it stating the theme header had already sent header information, and when I drill into the error, it relates to both WP and osCommerce trying to issue cookies from the same URL page.

OsCommerce then dies and the rest of the WP page fails to load (no posts etc). Switching back to script tags then runs the WP side of the page normally, but the products from osCommerce don’t display despite the code again being in the page source.

This is driving me completely nuts – I’ve spent 4 days trying to get it fixed … it gets worse ….

If I change the script to point at a different oscommerce/includes/boxes/filename.php file, that one then shows fully correctly but only allows display of a single product, not the 2×2 array of 4 products that I want from the original /boxes/filename.php

This then leads me to think that the problem overall lies within WordPress php-script handling system (it’s not javascript – its php script) because all parts of the oscommerce end are working correctly, but the desired content is not showing up in WP when more than one product is returned from the osCommerce database.

I’ve scoured wp.org and the forums and tried every fix listed thus far and nothing is curing this.

The theme in use is the excellent WyntonMagazine theme from https://www.der-prinz.com and I use it on several sites already, but this is a major rehack of it for this site.

Any help appreciated
Gaz

Why is this marked resolved? Read the last line of the second post !!

Just to reinforce that statement – I am having the same issues in WP2.8.4 and searching the forums finds hundreds of other threads with the same problem.

C’mon WP Devs – you can’t fix this problem by just marking topics as resolved when they are not.

There is a serious and fundamental problem in WP now with Javascript and it’s been running since at least v2.5 – according to my current project that I have spent 3 days trying to solve (without success), FireBug shows the page code has grabbed the data to be output and it’s fully formatted and ready to display, but WordPress just simply refuses to let it show up on screen. It displays fine if I access the script directly in the browser – everything is beautifully laid out (it’s a catalogue table from an oscommerce database) but WordPress says nope, no way, not gonna let you see it.

So, this topic is not solved as no working solution is posted in it.

Some help would be appreciated if anyone has this problem licked?