I have exactly the same site settings in coda 1.7.4 as I do in coda 2 but when I click the publish arrow in coda 2 it tells me "Set both local and Remote paths in a site to publish your changes".
I have already done that but it still is not working. As I said the same settings are in the older version and it works fine and publishes.
Anyone have any of the same problems.
I contacted Coda support for exactly this issue today... Same as you, after setting up a site with the correct remote and local roots - confirmed because I could connect to both - but still the publish window said "Set both local and Remote paths in a site to publish your changes".
Literally the solution was to close Coda down and re-open it. Apparently this is a known issue, when setting up a new site you have to restart Coda to use the publish functionality.
Just by closing Coda and restarting it the publish function now works for me.
I had this problem and none of the above worked. I got the following reply from the team at Coda and it worked a treat.
Right click the saved site in question and choose Edit. Disable publishing and automatic indexing.
Save and close the site
Open the site, then from the menubar choose File > Sites > Rebuild Site Index
After the indexing competes, restart Coda and then re-enable publishing (and optionally, automatic indexing)
I had the same issue until I ticked the "Use Publishing" in the site settings.
Check out the image: CODA 2 Site Settings
I can now publish via the ⌥⌘P on a Mac.
I hope this helps.
Specifically, you have to close all the open documents in Coda, reconfirm the local and remote directories configured for the site, then close Coda2 and reopen it.
Honestly, that a bug like this still exists, is amazing. After all these years, I still need to keep Dreamweaver around. Get with it Coda! #coda #coda2
My "fix" (this time) was:
to edit the FTP server's domain to be not working,
open the site,
let it complain the server is wrong,
close Coda,
reopen Coda,
fix FTP domain,
open site,
and voilà!
A classic I-learn-by-complaining case. ;-)
(Coda 2.6.10...)
I had a situation where the publishing had been working ok, and then mysteriously stopped.
I tried all the suggestions previously answered by BenLeah, Ben Darlington, Robert Barrueco, and Manu, and upgraded to the latest version of Coda2 (from 2.6.9 to 2.6.10), but none of these restored publishing.
What did finally work for me, was to physically delete the site connection panel in Coda2 and create a new site altogether (with the exact same settings). Not sure if this will work again if the publishing turns itself off again in the future, or if it solves the problem for anybody else. If it ever does, I'll update this answer.
It's unbelievable that Panic has not fixed this by now.
Finding and deleting every Coda related file and reinstalling Coda did not help.
My "fix" (this time) was to delete the site in Coda and recreate it.
Publish stopped working for one of my sites, but for entirely different reasons than others have discussed here. I used Time Machine to roll back to a recent version of the site, renaming the original folder so I would know not to use it. Coda 2, however, kept pointing to the original (renamed) folder.
So it seems Coda uses a unique ID to identify the local root folder, not a simple file path. This is probably a good idea in most cases—it means if you move or change the name of this folder in the Finder, Coda still knows where it is. But if the actual folder changes (as it will if you recover from a backup), you can expect the unexpected.
I still don't know why the publish feature stopped working with the renamed folder. (In some ways I'm glad it did, as it stopped me publishing from the wrong folder.) All I know is that updating the 'Local Root' of the site fixed the problem.
You have to set the FTP putting the mouse on the file between your site and the page. Below the menu, as soon as you click file you will open in the middle a screen. Then you put in your FTP settings.
Related
I'm using pgAdmin 4 (v. 6.12) on Windows 10.
Since (I believe) version 6.10 I've noticed that autocomplete always shows up. I tried to change preferences settings to only show it on Ctrl + space:
But it made no difference - autocomplete is always shown.
Then I've noticed, that some other settings are not respected, for example insert bracket pairs:
This is how editor looks just after typing opening bracket:
This is very annoying. I've completely removed previous installation of pgAdmin: uninstalled it, deleted all files and folders with pgAdmin in name and did the same in Windows registry. But new installation behaves the same.
New installation was made only for my user account, not for Anyone who uses this computer option.
Like you, I was also unable to turn off autocomplete-on-type after installing 6.12.
When using the web client, I was able to log out and log back in to solve it.
UPDATE from comments: using the Windows application, Adam was able to clean session data from the registry, open the editor window, change settings, close editor window, change settings… And it started to work again.
More details...
It happened to me in Ubuntu when I first upgraded to 6.12 and restarted the server, while the client was connected. The web client appears to have held on to a session that at first seemed to work. Once I logged out and log back in, my autocomplete-on-type OFF setting was respected again.
I agree that this bug is completely frustrating. I'm not sure why anyone would want the autocomplete-on-type setting enabled, pgadmin4 is unusable with it on.
I just came back from MWLUG and started to open up some Xpages DBs to work on, when all of the sudden I am getting 1000s of errors like this:
I googled the issue and I believe it has something to do with the path of the org.eclipse.pde.core.requiredPlugins.
When I opened up the packages and looked at fixing an error I got this:
The problem is that I do not know what the correct setting for this should be, or how to fix it. The apps run fine, but obviously something is wrong.
Any help would be very much appreciated.
Bryan
==================================================
I may know more about the problem. In designer when I go to File==>Application==Application Management this is what I see:
A different install has several components under it.
I updated my designer and client and admin to 9.0.1 FP4 last week. That is the last thing I remember doing before this messed up (along with installing the Debug Toolbar).
How can I fix my designer install?
Strange indeed, you should check your hard drive for bad sectors.
Looks like a broken DDE in general. The plugin XML file maybe broken so the app manager doesn't show you the plugins installed. Therefor I assume DDE starts very quickly, right? Because nothing is loaded.
I had this before and my "solution" was:
de-install DDE and Fixpacks
delete workspace folder
re-install DDE and Fixpacks
re-install plugins ad setup workig sets
This is a pity but at least you get a clean install. You don't have to delete everything (e.g. the DATA folder)
When I use WebMatrix (the latest version, on Windows 8 RP) to try to connect to an FTP site, it shows an error where files should be shown. I actually have no idea what could be causing this, and I can't find any log file that could help. Screenshot: http://imgur.com/aV7iR
I'm also using IIS 8 to host a local PHP/MySQL site, if that matters
Thanks,
Matthew
I think this might actually be a different issue. There is a bug in WebMatrix RC that causes the remote view to behave badly when connecting to directories with large numbers of files.
We've fixed this now, and it should not repro in our next release. Sorry for any inconveniences this has caused.
Ah, it turned out to be because I had a file called "CFLogo.png" and another file called "cflogo.png" on my server and WebMatrix wasn't able to deal with both of them having essentially the same name :\
The following issue just crept up on me. The steps mentioned below had worked just fine until about 2 days ago.
When I deploy a update to a solution (of web parts) to a SharePoint 2010 server I don't see the update. The solution does get installed, but from what I can tell the installed web parts are over a month old (nothing new is installed).
I do the following steps through PowerShell:
retract the solution from the web app
remove the solution
add the solution
install the solution to the web app
I have tried restarting the Web App, restarting IIS and also restarting the server. Nothing seems to work.
I notice that after I remove the solution it does get removed from the GAC. After I add/install it the solution does reappears in the GAC.
Am I missing something? Am I overlooking a step that I should be doing? Something to try?
I never deactivated/reactivated the Feature.
After following the same steps I mentioned in my question I just deactivated, then reactivated, the Feature and everything started to working fine.
This is an easy thing to I can start to implement with my solution updates. However, why did I never have to do this step before?
In general, you should check your ULS log to see which version of your solution is running. If you see the old one, then you can be sure that your activated site feature is still bound to the old version. In this case you have to Inactivate the site feature indeed to loose that tie and then Activate to bind to the new one (it appears Activate always ties the site feature to the newest version of the solution).
Maybe you had not to do this earlier, because you did not change the version number of your solution, appearing as the same version in GAC on the server. In this case you had your site feature already pointing to the correct version of your solution, therefore didn't have to reset the feature.
You have probably checked, but just in case. Make sure that the powershell script is not adding a month old package.
Is the problem in the web part code or the configuration? The configuration usually unghosts itself sooner or later and refuses to update from the solution - you can update the file in the gallery manually if anything has changed there. For most updates there won't be any changes because existing web parts won't get updates applied anyway - they will use new code but old configuration.
If the problem is the code itself, does the assembly appear to the system to be unchanged? All the hardcoded full name references in SharePoint config files mean that usually you are deploying a new assembly but with the same version numbers. This can mean that the system doesn't bother making the update. I have found it very useful to update AssemblyFileVersion (which does not affect binding) on every build and have a page in _layouts that displays the file versions of all the loaded assemblies so I know exactly what is running.
I recently switched from Vista to Windows 7 (with IIS 7.5). But i can't seem to get it fully working.
My problem: I run Visual Studio 2008 (sp1) (run as administrator) and i see my WebSite (webforms).
I publish my website, and all seems well, except my layout is wasted.. why? i get a 404 on my CSS and javascript file.
I read an article that you need content server (service?) installed. After some translation i figured that should be "Statische inhoud" (dutch.. translated static content).
I triple checked that the .js and .css files are in te folder i'm pointing to (tried root folder of the website), but all in veighn...
Here is my IIS-component list that is installed (in dutch).
Anyone able to figure out why i get 404's? or even beter, how do i fix it?
http://img69.imageshack.us/img69/4026/iis.png
I had this problem and spent 6 hours doing research and trying out many suggested solutions.
We resolved this by granting the default IIS user access to the application folder.
Well, i finally figured it out :)
Hope some else will be helped by this answer:
It was related to the Static File Module.
Microsoft has a solution which did not work for me.
http://support.microsoft.com/kb/942052/
It was already configured this way.
But i deleted it, added it again, i could access my CSS... but ASPX didn't work anymore. The Fix for that issue: Make the list Sorted, and move your static filehandler to the bottom (or a least after aspx, but probably the best is at the bottem).
Thanxs everyone for the pointers though!