Unfortunately I am getting occasional 404 errors from admin-ajax.php.

The request seems to be sent and processed because on refresh of the page I can see the updates. However it is a bad user experience because the user’s page just stalls.

After a little troubleshooting, mainly with crude debug statements from admin-ajax.php into HTTP headers, I have noticed that admin-ajax.php is not even entered.

At the moment I am not sure whether the error is related to one of the WordPress plugins I am using or whether it is due to my webhost.

There are no visible errors in weblogs nor in error_log.

One thing I noticed that a new incognito browser window resolved the issue.

This made me suspicious of cookie issues. I manage to narrow it down to the PHPSESSID cookie. Clearing it resolved the issue. The 404 error from admin-ajax.php is gone… for a while at least.

I recommend using the excellent Eat This Cookie extension If you are using Chrome or Brave browser.

The search continues…

The post 404 errors from admin-ajax.php in WordPress appeared first on The Story of David Kaspar.

In my judgement the overall planning balance is heavily weighted against the scheme. The manner in which the present proposals respond to the attributes and address the constraints of the site has sacrificed many environmental quality objectives for the sake of maximising the amount of accommodation. I conclude that the appeals should be dismissed and that planning permission should be refused

Have a look at the SRRA summary or download the inspectors full report.
I have learned that the democratic system is a double-edged sword. While it gave us residents an opportunity to affect the local council in their decision, it also gave the developers right to appeal a chain of decisions against their “monstrous” plans. (However their practice of submitting dual identical applications in order not to give the council a chance to reply in assigned time and thus escalating the matter was less than honest.)
The victory would not have been possible without the organisation skills and eloquence of local resident Phillipe Auclair. As another resident put it, “A whole lot of people were doing their bit but without Phillipe’s help we would not have known what our bits were”. Phillipe’s eloquence was both a motivator to all of us and a stinging to the developer’s arguments.
“Is this the end?” one of the local residents asked. “It’s more like the beginning of a long struggle to keep the woodland unharmed” was the consensus of the groups leading group.

The post Put Champagne on ice appeared first on The Story of David Kaspar.

The post Netbeans 3.6 appeared first on The Story of David Kaspar.

The CVS integration is great as it lets your check in and out source files directly from the development environment. I have only tested it together with Microsoft VSS (what a pain that is btw) but it supports other CVS profiles. While it is handy it can be a bit slow on large directory structures so I tend to use it for single files only. When I want to manipulate large amount of source files, I use the VSS client instead.
NetBeans has good XML and XSL support. It lets you validate your XML documents and you can do XSL transformations right there in the IDE. No XSLT debugging though, so get your self a decent XSL IDE (XML Spy or Xcelerator) for serious XSLT.
Javadocs are always tedious to write but NetBeans makes your life little bit easier. It has a nice JavaDoc GUI where all the important fields are listed. It can also auto correct missing fields for you which again saves time.
Ant is integrated in a way that you can browse your build.xml files and execute specific targets.
If you ever need to write localised property files NetBeans helps out with that as well. It will display keys and the various localised values in a matrix, making it easier to modify them all at once.
The GUI Editing in NetBeans looks extensive but I have not got around using it since all work has been web related and did not include any AWT or Swing coding.
There are some disadvantages that I have found. I miss a refactoring functionality the most. Other IDE’s (eg IntelliJ) have features like “find usages” of a method or “refactor” that lets you change package and method names across the whole source. With NetBeans, I have to use the “Find…” functionality and manually make any changes.
Large projects often have source code across multiple modules and directories but are built into one single directory structure. One approach that other IDEs take is that they allow you to set up matching patterns on where to build a source. You probably want different directories for Servlets and other front-end classes, libraries and EJBs. NetBeans is very difficult to set up to build to multiple targets. One has to basically manually specify the build directory for each source file… time consuming.
I also miss J2EE support (templates, wizards). Having grown custom to Borland JBuilder‘s J2ee support I find some task very repetitive and manual in NetBeans.
Another new and upcoming OpenSource IDE is Eclipse. Some knowledgeable people (Sean and Matt) have been swearing by it, saying that it is indeed better than NetBeans. I had a brief look at it but because the UI and other crucial details seems to be working differently I did not dare to use it for actual development yet.

The post Netbeans IDE, pros and cons appeared first on The Story of David Kaspar.