jokerbr313

This is a nice example of the plugin’s feature. If it’s alright with you, when I get around to making a proper wiki section, can I use this or use it as a reference? Considering you put the time into composing it, I figured it would be proper to ask.

Thank you for posting this topic.

jjyepez, thank you for the reply and for taking the time to make a how-to topic in another thread. I had to take a bit of a break and let my mind unwind. So me being the only developer, I had to leave everything as-is for the time being, but at the current moment, I’m back to getting another update ready for release to further stabilize version 0.3.

yyyyyywhy, sorry for the late reply. I think this question was asked during a development period and I didn’t have any useful info I could give at the time. The function he mentions though is a function from Kalin’s Post List that I had preserved, but haven’t had the time to fully check out and create a wiki for.

Anyways, thanks for the comments.

Oh ok. I was kinda hoping you’d be the first to try it out and give me feedback on it before I mark it as the next beta release.

Anyways, I currently working on getting a WordPress site setup and going public with it. I’ve mainly been waiting til I got custom posts and taxonomy support for my plugin before I established a public site again. All the plugins and themes I came across didn’t have the type of post lists support that I was looking for, and Kalin was originally the one to give the plugin a great start and show a lot of potential. So I had to wait. I’m just glad to I decided to author an alt version of the original. It’s been quite the experience =)

So, it might not be too long til I reply back with a direct link…and I’ll be switching from the current ‘free’ community forum to a WordPress platform with a forum built into it eventually. That mainly has to do with the fact that I need a website that I can also demonstrate this plugin. Along with other reason for centralizing things.

Glad to hear that your host might be able to help you out. Although, in some cases, he shouldn’t have to. On the other hand, he could have the timeout setting ridiculously low, but idk. This plugin has a lot of power to it, and it could be easy to make it a beast, and I already understand there’s some downsides if you get too carried away with designing basic code to get things started. Which, ultimately, thank you again for bring this to my attention. So far, your the only one to report this though…

Wow, time really has been flying by. Yet, another update, and sorry about the time that it has taken.

I have the plugin pretty much updated and finished to release the Beta 4 version, but I’m still a little on edge about it, and I don’t want to release it to the public until I am 100% comfortable with it this time. So, right now I’m working on a bunch of other things that relate to getting a WordPress environment setup. Plus there’s a bunch of other stuff that I’ve been wrapped up in. So there were a few times I had to take a break from the plugin.

All-in-all, things look good, but I’m still a lil iffy about it fixing your error. What I did was lighten the load on the memory, and try to process the data a little quicker. For example, some functions return values quicker depending on how much processing the function needs to do at the time.

Pretty much letting you know that I have not forgotten about you. If you want, I can send you a copy of the beta 4 version via email so you can give it a go, but I also prefer not to share my email address on this site. I currently have a free forum that I’m using to swap files and messages, but unfortunately, it requires registration (which we all get tired of going through), and I don’t have a direct link for the download (its still just on my computer). Again though, sorry about the delay.

The Community Forum

That’s a pretty interesting solution xP

Although I hope everything matches up fine for you. I haven’t looked much into the other plugin, but I might end up giving that a shot as well.

I also second that statement. I haven’t been able to use this plugin, but from what I’ve seen with the screenshots. I was quite impressed…then I saw the feedback =/

I figured I would reply considering your last question. I took a quick look at the plugin, and it seems fairly simple, but I haven’t got the time to look deep into it and debug it. Plus, I’m currently still working on updating my own plugin.

…but if you wanted to try and troubleshoot it or attempt to fix the problem…and I don’t even know what kind of experience you currently have. The quickest way, so far, is to locate and debug the scripts. With Chrome you just right-click->inspect element, click scripts, and then locate where the plugin’s scripts are. You may have to refresh the page after inspecting to see the scripts. If the problem doesn’t exist in the scripting (which, btw, the plugin uses quite a bit of scripting, so it wouldn’t surprise me if it is the problem), then you’ll have to debug the php part of it (which may also include debugging in WP files).

To debug in php I would recommend setting up a localhost on your computer, installing XDebug, and installing an IDE (preferably Netbeans). For a beginner, it’s not something you would consider easy, and after have saying all this. I wouldn’t be surprised if I turned you away from it. Although I would encourage it.

Anyways, I hope Pollyplummer continues this plugin. I just wish I had a chance to be able to personally check it out. For now I gotta move on…

Just giving you another update…

I’ve redesigned some of the main functions that support the custom post types and taxonomies. Post_Types->Taxonomies->Terms are the main 3, and the ‘get’ functions for them have been slimmed down tremendously to only get what is required for the plugin. It also allows for a lot more adaptability for future upgrades/updates. The other one I still need to code is the functions to get the current post attributes and post type pages (not posts).

Right now I’m solely working on functions that have relations to /wp-includes/post.php

Ok, just another update…since I have another idea that I was planning on doing in the next subversion anyways. I took a closer look at wp-includes/posp.php and I noticed that I use some of the functions within the file. Which I didn’t think would have ‘post-type’ functions.

What I’m going to do is slim down the functions to use only what is necessary instead of using the whole object (which mainly means using WordPress functions that don’t return objects, I was using get_post_type_object($args) for instance), and also separate some code into different functions. I had most of the varibles in the plugin slimmed down, but something in post.php is hanging.

After this, I’m out of ideas til I can think of something else. I think its server based. After you told me where it was coming from I started thinking it could be a function in the file, looking at it now, it very well could be the case. I was already planning on slimming down functions and variables, so I’ll give it a shot.

That’s pretty lame. The hosting that I have you can modify the file.

Is there any way you could ask the hosting admin to grant you access to modify it? Cause it could troubleshoot your problem. If not, my guess is that they are throttling your site.

If you do plan on going to a dedicated hosting service. It would probably be a good call to make.

Well, I’m kind of running out of time to explain it in my next post since i’m about to head out for the evening…but have you made any changes to the php.ini file?

Is that all the error says? and it only happens on the plugin admin page?

Ok, the next beta just got uploaded.

The Debug mode in WordPress might give you an error that I can work with. It isn’t something I recommend using on a public site, but its ultimately up to you if you want to use it. A lot of the times I just create an exact copy of the site’s files and database, and then put it on a localhost (requires some code to be changed in order to make the switch though). After that, I do a step by step debug run with an IDE. The timeout error isn’t much to go by, so a lot of it is guess work, assuming it is related to the plugin.

I doubt it has something to do with the amount of categories and posts, although I can’t rule it out completely. I used a ton of categories to make up for the loss of the post type & taxonomy support in 0.2, and I didn’t encounter a timeout error while working on 0.3, but not everyone’s problem is the same.

My main worry however, whether it’s the problem or not, is the plugin’s database. Although, so far, it looks like things are good. My second main worry though is the WordPress scripting support, but the only thing that relies on scripting while loading the page is the preset database table, and nothing needed to be altered in that part of the JavaScript (still the same as you might of noticed)…but the timeout error does have a relation with scripting. Another problem is that you may need to optimize your (phpMyAdmin) database. Since it’s on the same server, its got me wondering if the database might be a lil jumbled up.

At the moment, I’m working on uploading a new beta version. There were a few things that were throwing ‘strict’ errors that I fixed up. So if you do plan on using debug mode to see if you can catch an error, I strongly advise updating to Beta 3 first, AND using it as brief as possible.

define('WP_DEBUG', true); Should be the only thing you need to add or change to get it started.

I would also recommend changing error_reporting() in <em>site name</em>/wp-admin/load-scripts.php, and, optionally, <em>site name</em>/wp-admin/load-styles.php to…
error_reporting(E_ALL | E_STRICT);, but depending on what other plugins you have, you might catch a lot of other plugin errors.

Btw, I found some problems with Activate, Deactivate, and Delete/Uninstall action hooks. So after you update to Beta 3, if you could trouble shoot it one more time by restarting it, it should work and give you a clean install to work off of. Sorry, I took a deeper look into it and also found a bug while handling the action hooks.

Just to give you an update…

I’ve been looking into the issue trying to figure out what the source could be, and it could also be host related (mainly GoDaddy). I’ve notice a lot of other people recommended modifying the php.ini file’s max_execution_time. I’m also going through the plugin and writing in some safe-guards, but I was wondering, do you know how to turn on Debug in WordPress?

Sorry I don’t have any more info on this as of yet. Spend most of the day going through the plugin and correcting some things that might be a possible issue. I should have an update available soon though.

Glad you love the plugin. Sorry about the issue though. I hope you backed up your presets prior to upgrading though.

It could be a number of reasons why your getting that error. The most likely reason is that your getting hung up on something (a loop). It may be a script error, or a script getting an error from some backend code, or maybe something in constructing the settings page. Its hard to tell on my end, but you said this problem only exists on the plugin’s setting page, right?

Here’s a couple other questions…
Have you tried disabling other plugins to see if the plugin would work?
Have you tried selecting “Yes” on “Delete preset upon deactivation” and then deactivating and then reactivating the new plugin version (it should give it a fresh install)?